AM-326 ams:Introduce trace id identifier in logs #458
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a new parameter that should be present in all logs that take place after a user has executed any request against the system.
The trace_id parameter will assist in grouping logs of the same originator making it easier to check what happened during a specific flow.
The most idiomatic way to add request-scoped parameters is through the standard context package.
It's common in go to propagate context as a first parameter in each function.
The biggest change is the store interface which had all its methods to accept a context as first argument.
This change also helps in the migration to the new mongo official driver, which expects context on all its calls.