Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support events.causation_id #45

Closed
harukizaemon opened this issue Apr 16, 2017 · 2 comments
Closed

Support events.causation_id #45

harukizaemon opened this issue Apr 16, 2017 · 2 comments
Labels
enhancement

Comments

@harukizaemon
Copy link
Contributor

In addition to correlation_id for tracing a thread of execution, in a number of production systems we've found it helpful to also have a causation_id being the ID of the message that directly triggered the creation of the events.

To implement, this is usually a matter of not only copying the correlation_id from the inbound message but also populating the causation_id from the ID of the message itself.
@slashdotdash
Copy link
Member

I'll add this to the backlog. For now, you could include the additional causation_id property in the event metadata.

@slashdotdash
Copy link
Member

Done by @harukizaemon in #48.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@harukizaemon @slashdotdash