-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MTTL-376 Setup boiler plate code for logging the correlation ID #2
Conversation
using Microsoft.AspNetCore.Routing; | ||
using NUnit.Framework; | ||
|
||
namespace BaseApi.Tests.V1.Controllers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The folder names need to be changed (both BaseAPI
and BaseAPI.Tests
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Happy to do so, but if possible we should merge the initial renaming PR. And then I can merge master from there to this branch which should resolve it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I forgot the renaming PR hasn't been merged, ignore this comment please
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No worries at all :) With 2 approvals, I took the liberty of merging the renaming PR to master and then into this branch. Renaming issues should be resolved by now.
Link to JIRA ticket
https://hackney.atlassian.net/browse/MTTL-376
Describe this PR
PR to add correlationId for every incoming request.
What is the problem we're trying to solve
CorrelationId will be used as part of our logging strategy. By including a CorrelationId with logs we will be able to trace individual requests during debugging/monitoring attempts.
What changes have we introduced
Checklist
Follow up actions after merging PR
Are there any next steps that need to addressed after merging this PR? Add them here.