search

jaegertracing / jaeger-ui

Web UI for Jaeger
http://jaegertracing.io/
Apache License 2.0
1.11k stars 475 forks source link

[Bug]: Can't find services for old traces #1628

Open TheOxFromOutOfTheBox opened 1 year ago

TheOxFromOutOfTheBox commented 1 year ago

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

image

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

docker run -d --rm -it --link=elasticsearch --name=jaeger -e SPAN_STORAGE_TYPE=elasticsearch -e ES_SERVER_URLS=http://10.0.2.15:9200 -e ES_TAGS_AS_FIELDS_ALL=true -p 16686:16686 -p 14250:14250 jaegertracing/all-in-one:1.45
serban-nicusor-toptal commented 4 months ago

I'm running now into a similar problem after migrating to a different ES cluster. Did you manage to find the culprit @TheOxFromOutOfTheBox ?