-
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
Implement basic request tracing capabilities #303
Labels
LAPIS
Tasks/PR related to LAPIS
Comments
fengelniederhammer
added a commit
that referenced
this issue
Feb 27, 2024
fengelniederhammer
added a commit
that referenced
this issue
Feb 27, 2024
fengelniederhammer
added a commit
to GenSpectrum/LAPIS
that referenced
this issue
Feb 27, 2024
1 task
fengelniederhammer
added a commit
that referenced
this issue
Feb 27, 2024
fengelniederhammer
added a commit
to GenSpectrum/LAPIS
that referenced
this issue
Feb 27, 2024
fengelniederhammer
added a commit
that referenced
this issue
Feb 27, 2024
fengelniederhammer
added a commit
to GenSpectrum/LAPIS
that referenced
this issue
Feb 28, 2024
This was referenced May 7, 2024
This was referenced Sep 12, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related to #298, we need to be able to trace requests in the logs. We should at least be able to correlate incoming request and outgoing response.
Idea: Implement the
X-Request-Id
header.The text was updated successfully, but these errors were encountered: