As a Jaeger user with Elasticsearch as a backend
I want the Jaeger UI to respect ES_TAGS_AS_FIELDS_DOT_REPLACEMENT
So I can use sophisticated UI functionality while using Elasticsearch as a backend
This only seems to occur when using a custom label, e.g _ rather than the default @. We've now switched to the default so are less interested in the resolution of this.
What happened?
As a Jaeger user with Elasticsearch as a backend I want the Jaeger UI to respect ES_TAGS_AS_FIELDS_DOT_REPLACEMENT So I can use sophisticated UI functionality while using Elasticsearch as a backend
Currently, https://github.com/jaegertracing/jaeger-ui/pull/659 is not working due to
peer.service
becomingpeer_service
(similar with other special functionality/fields implemented here: https://github.com/jaegertracing/jaeger-ui/blob/e197d1c8d36a73616620c2b4d55d18f4a017a188/packages/jaeger-ui/src/model/trace-dag/denseTransforms.tsxSteps to reproduce
ES_TAGS_AS_FIELDS_DOT_REPLACEMENT="_"
on the collectorspan.kind=CLIENT
,peer.service=PeerService
Expected behavior
I'd expect the PeerService to be shown as per this PR https://github.com/jaegertracing/jaeger-ui/pull/659
Relevant log output
No response
Screenshot
peer.service
is converted topeer_service
, so the code path is not triggered.Additional context
No response
Jaeger backend version
v1.37.0
SDK
OpenTelemetry Java Agent v1.17.0
Pipeline
OTEL SDK -> OTEL Collector -> Jaeger Collector -> [Jaeger Proto] -> Elasticsearch (AWS Opensearch 1.3)
Stogage backend
AWS Opensearch 1.3
Operating system
Linux
Deployment model
Docker ECS Daemons
Deployment configs