Allow trace information to be attributed to a request #103
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.
This PR makes it possible to attribute trace events to the specific request that triggered the activity.
The key changes here are:
Impulse
now has a.session_id()
method that allows you to check the session identifier of any entry in a chain of impulsesRecipient
providessession
information which provides a root session for the entire impulse chain. Every service and workflow session produced as part of the requested impulse chain will be a descendant of this session.OperationStarted
event now shows the whole stack of sessions that led to the operation.OperationStarted
is equal to the recipient session of the impulse chain.