Messaging.message.conversation_id visible in Traces but not searchable in Discover

Elastic Observability APM
1

Hi everyone,

We're using the JMS Correlation ID in our application. In Elastic APM / Traces, I can see the field and its value on individual spans in the field: attributes.messaging.message.conversation_id

However, I cannot search or filter on this field in Discover. Our goal is to use the JMS Correlation ID to find all related traces and messages.

A few questions:

  1. Is messaging.message.conversation_id intentionally stored as metadata only?
  2. Is there a supported way to make this field searchable in Discover?
  3. Can this be achieved without creating custom Elasticsearch mappings or modifying the managed APM data stream templates?

We would prefer to stay with the managed Elastic APM / OpenTelemetry mappings and avoid maintaining custom index templates if possible.

Thanks!

2

That's an otel field, I need more info on your architecture. Which agent (edot/otel/apm) and version, and which endpoint, apm server/edot collector/custom collector and version?

3

Hello Jack,

We are using the Elastic Distribution of OpenTelemetry Java (version 1.11.0) in our application and are sending the telemetry data directly to our serverless Elastic Observablility instance, so the managed OTLP endpoint of Elasticsearch.

4

In Discover, making sure you have the time range correctly set to cover the traces, when you try the KQL
attributes.messaging.message.conversation_id: "ID:your-correlation-id"

or

messaging.message.conversation_id: "ID:your-correlation-id"

that doesn't give you anything? (make sure you are searching the maximal index set traces-* otel-*)