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

Improve traces behavior on component failure #1360

Open
JulianVentura opened this issue Nov 4, 2024 · 0 comments
Open

Improve traces behavior on component failure #1360

JulianVentura opened this issue Nov 4, 2024 · 0 comments

Comments

@JulianVentura
Copy link
Collaborator

JulianVentura commented Nov 4, 2024

Jaeger will only show traces if they are created and finished.
Currently, we have two scenarios on which a failure in the tracker implies loss in traces.

  1. If the tracker is down when a new trace is going to be created, the call will fail and the trace won't be created. The tracker may get up and receive requests related to that same trace, but will ignore them since it hasn't been created.
  2. If the tracker is down when a trace is going to be finished, the call will fail and the trace won't be finished.

On both cases, the trace will be lost and with it valid information that could be saved otherwise.

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

No branches or pull requests

1 participant