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

Implement basic request tracing capabilities #303

Closed
fengelniederhammer opened this issue Feb 27, 2024 · 0 comments · Fixed by #304
Closed

Implement basic request tracing capabilities #303

fengelniederhammer opened this issue Feb 27, 2024 · 0 comments · Fixed by #304
Assignees
Labels
LAPIS Tasks/PR related to LAPIS

Comments

@fengelniederhammer
Copy link
Contributor

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.

  • If it is set, SILO will take the value.
  • If no value is set, SILO will generate a value
  • The response should contain the request id
  • At least one log statement should log the request ID along with some indication on the request itself
  • At least one log statement shoud log the request ID along with some indication on the response.
@fengelniederhammer fengelniederhammer added the LAPIS Tasks/PR related to LAPIS label Feb 27, 2024
@fengelniederhammer fengelniederhammer self-assigned this Feb 27, 2024
fengelniederhammer added a commit to GenSpectrum/LAPIS 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 to GenSpectrum/LAPIS that referenced this issue Feb 28, 2024
@github-actions github-actions bot mentioned this issue Aug 6, 2024
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
LAPIS Tasks/PR related to LAPIS
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant