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

Log with correlation_id throughout the ingestion process #11

Closed
juhtornr opened this issue Jan 2, 2019 · 2 comments · Fixed by #86
Closed

Log with correlation_id throughout the ingestion process #11

juhtornr opened this issue Jan 2, 2019 · 2 comments · Fixed by #86
Assignees
Labels
version 2 Task saved for version 2

Comments

@juhtornr
Copy link
Contributor

juhtornr commented Jan 2, 2019

Issue by viklund
Friday Sep 21, 2018 at 08:30 GMT
Originally opened as NBISweden/LocalEGA#363


Description

Currently it's difficult to follow a file through the ingestion process from the logs. Adding the correlation_id from rabbitmq will solve this.

DoD (Definition of Done)

All log lines from ingestion contains correlation_id somewhere.

Testing

Look at the logs when running make in the docker/test directory.

@juhtornr juhtornr added this to the Sprint 37 milestone Jan 2, 2019
@silverdaz
Copy link
Contributor

Code ready, but not merged.
Testsuite is also adjusted to use correlation id for tracking MQ messages, and not specific message content.
One can look at the debug output from the testsuite.

@juhtornr
Copy link
Contributor Author

juhtornr commented Jan 18, 2019

Time estimate: 0.5 days

@silverdaz silverdaz added the version 2 Task saved for version 2 label Feb 20, 2019
@silverdaz silverdaz mentioned this issue Dec 8, 2019
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
version 2 Task saved for version 2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants