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.

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

Merged
merged 9 commits into from
Feb 20, 2025

Conversation

@jonny-mccoubrey jonny-mccoubrey self-assigned this Feb 6, 2025
@buildmachine-sou-jenkins2
Copy link
Contributor

@jonny-mccoubrey
Copy link
Contributor Author

StreamingWorkerWrapper::run() actually already adds the correlation-id to MDC in workers:
image

@jonny-mccoubrey
Copy link
Contributor Author

Description of Changes

Pre-existing correlation ID logic

As 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 MR

There 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).

@jonny-mccoubrey jonny-mccoubrey merged commit 8a647ae into develop Feb 20, 2025
1 check passed
@jonny-mccoubrey jonny-mccoubrey deleted the US990352 branch February 20, 2025 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants