-
Notifications
You must be signed in to change notification settings - Fork 3
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
US990352: Correlate specific documents with audit events #216
Conversation
This reverts commit 6fc942d.
StreamingWorkerWrapper::run() actually already adds the correlation-id to MDC in workers: |
Description of ChangesPre-existing correlation ID logicAs the comment above shows, worker-framework already has logic that takes correlation id from the incoming worker task and sets it in the MDC context. Changes in this MRThere was also logic present in workflow-worker that checked the custom data for a correlation id. The MDC context would then be overwritten with the correlation id in custom data or else one was generated - this was overwriting the existing worker-framework code mentioned above. The changes in this MR fix this so that if a correlation ID has been set in the MDC context, this is set in the custom data of the outgoing message (otherwise one is generated and set). |
https://internal.almoctane.com/ui/entity-navigation?p=131002/6001&entityType=work_item&id=990352