-
Notifications
You must be signed in to change notification settings - Fork 470
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
[Bug]: Can't find services for old traces #1628
Labels
Comments
I'm running now into a similar problem after migrating to a different ES cluster. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
When I try to search for traces that occurred like 3-4 days in the past (and not running since I restarted my jaeger instance) , I can't find the service to search for the required traces.
Steps to reproduce
Run Jaeger with Elasticsearch backend.Execute some program sending traces once. This will store the traces in a daily created jaeger index, along with the another index for service.
Then wait for next day, restart Jaeger and try to fetch the output from the previous day without having run the program which created old services.
Expected behavior
I should see the old services in my dropdown list to select, but I don't.
Relevant log output
No response
Screenshot
Additional context
No response
Jaeger backend version
v1.45.0 (Docker version)
SDK
OpenTelemetry SDK
Pipeline
OTEL SDK -> OTEL Collector -> Jaeger all in one -> Elasticsearch
Stogage backend
Elasticsearch v7.17.10
Operating system
Linux
Deployment model
Docker
Deployment configs
The text was updated successfully, but these errors were encountered: