[Bug]: jaeger UI doesn't populate service dropdown correctly

[mulpk]

What happened?

Jaeger UI doesn't populate the new service name added in the dropdown even though I can see it in opensearch.

not sure if it matters but I have below flag enabled as the clusters are setup for cross cluster search
es.remote-read-clusters: *

jaeger UI display data from all clusters and I can lookup traces fine.

Steps to reproduce

• add a new service name to the trace
• it doesn't appear in jaeger ui service dropdown

Expected behavior

• add a new service name to the trace
• it should appear in jaeger ui service dropdown

Relevant log output

Screenshot

No response

Additional context

No response

Jaeger backend version

v1.37.0

SDK

No response

Pipeline

No response

Stogage backend

OCI Opensearch

Operating system

Linux

Deployment model

binaries

Deployment configs

[yurishkuro]

Did you refresh the UI? How long did you wait after sending the trace?

[mulpk]

we added the service name couple of weeks ago and I did refresh the jaeger UI but it didn't help

I can see the new service name in opensearch dashboards from the time it's added but not in UI.

does the jaeger UI has cache or something?

only thing I didn't do is restart jaeger UI.. do you think it will help?

[yurishkuro]

only thing I didn't do is restart jaeger UI.. do you think it will help?

Worth a try, if for some reason the refresh background thread died on an error. Service names are usually cached in the query service because loading them from DB on every UI access it rather slow.

If restart helps we have a bug somewhere.

[mulpk]

we restarted the jaeger ui but it didn't help

[mulpk]

@yurishkuro anything else we can do to troubleshoot the issue further?

[yurishkuro]

Does that service name appear in the spans with correct timestamps? E.g. you could have a bug in the instrumentation that reports out of range timestamps that are not found by the search queries.