# Messaging.message.conversation\_id visible in Traces but not searchable in Discover

**URL:** <https://discuss.elastic.co/t/messaging-message-conversation-id-visible-in-traces-but-not-searchable-in-discover/390038>\
**Category:** APM\
**Tags:** java\
**Created:** [September 1, 2026, 9:34am UTC](https://discuss.elastic.co/t/messaging-message-conversation-id-visible-in-traces-but-not-searchable-in-discover/390038 "2026-09-01T09:34:12Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![ex.ko](https://avatars.discourse-cdn.com/v4/letter/e/90db22/32.png) [@ex.ko](https://discuss.elastic.co/u/ex.ko)\
**Post date:** [September 1, 2026, 9:34am UTC](https://discuss.elastic.co/t/messaging-message-conversation-id-visible-in-traces-but-not-searchable-in-discover/390038/1 "2026-09-01T09:34:12Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![Jack\_Shirazi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_shirazi/32/91641_2.png) [@Jack\_Shirazi](https://discuss.elastic.co/u/Jack_Shirazi)\
**Post date:** [September 1, 2026, 1:26pm UTC](https://discuss.elastic.co/t/messaging-message-conversation-id-visible-in-traces-but-not-searchable-in-discover/390038/2 "2026-09-01T13:26:24Z")

</div>

That's an otel field, I need more info on your architecture. Which agent ([edot](https://github.com/elastic/elastic-otel-java)/[otel](https://github.com/open-telemetry/opentelemetry-java-instrumentation)/[apm](https://github.com/elastic/apm-agent-java/)) and version, and which endpoint, apm server/edot collector/custom collector and version?

---

<div class="post-metadata">

**Author:** ![ex.ko](https://avatars.discourse-cdn.com/v4/letter/e/90db22/32.png) [@ex.ko](https://discuss.elastic.co/u/ex.ko)\
**Post date:** [September 1, 2026, 1:55pm UTC](https://discuss.elastic.co/t/messaging-message-conversation-id-visible-in-traces-but-not-searchable-in-discover/390038/3 "2026-09-01T13:55:04Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Jack\_Shirazi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_shirazi/32/91641_2.png) [@Jack\_Shirazi](https://discuss.elastic.co/u/Jack_Shirazi)\
**Post date:** [September 2, 2026, 1:47pm UTC](https://discuss.elastic.co/t/messaging-message-conversation-id-visible-in-traces-but-not-searchable-in-discover/390038/4 "2026-09-02T13:47:50Z")

</div>

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-*`)

---

<div class="post-metadata">

**Author:** ![ex.ko](https://avatars.discourse-cdn.com/v4/letter/e/90db22/32.png) [@ex.ko](https://discuss.elastic.co/u/ex.ko)\
**Post date:** [September 3, 2026, 11:09am UTC](https://discuss.elastic.co/t/messaging-message-conversation-id-visible-in-traces-but-not-searchable-in-discover/390038/5 "2026-09-03T11:09:26Z")

</div>

Thanks for the advice. I tried doing that but I can't access the field `attributes.messaging.message.conversation_id` in Discover.

Here the `attributes.messaging.message.conversation_id` seen in the transaction details.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/b/2bb516adc9346c397a80e76d4d07c7dcf1eb7935.png)  
And here you can see I searched the same span using the span id and tried to find the field `attributes.messaging.message.conversation_id`.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/8/98a8d31f6a839970338d46107f3503b2ae839e8f.png)

---

<div class="post-metadata">

**Author:** ![Jack\_Shirazi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_shirazi/32/91641_2.png) [@Jack\_Shirazi](https://discuss.elastic.co/u/Jack_Shirazi)\
**Post date:** [September 3, 2026, 11:32am UTC](https://discuss.elastic.co/t/messaging-message-conversation-id-visible-in-traces-but-not-searchable-in-discover/390038/6 "2026-09-03T11:32:32Z")

</div>

It doesn't have `attributes.messaging.message.conversation_id` but does it have `messaging.message.conversation_id` or `labels.messaging.message.conversation_id`?

---

<div class="post-metadata">

**Author:** ![Jack\_Shirazi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_shirazi/32/91641_2.png) [@Jack\_Shirazi](https://discuss.elastic.co/u/Jack_Shirazi)\
**Post date:** [September 3, 2026, 12:35pm UTC](https://discuss.elastic.co/t/messaging-message-conversation-id-visible-in-traces-but-not-searchable-in-discover/390038/7 "2026-09-03T12:35:40Z")

</div>

> [@ex.ko](#):
>
> ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/8/98a8d31f6a839970338d46107f3503b2ae839e8f.png)

Which index was the span document found in?

---

<div class="post-metadata">

**Author:** ![ex.ko](https://avatars.discourse-cdn.com/v4/letter/e/90db22/32.png) [@ex.ko](https://discuss.elastic.co/u/ex.ko)\
**Post date:** [September 3, 2026, 1:14pm UTC](https://discuss.elastic.co/t/messaging-message-conversation-id-visible-in-traces-but-not-searchable-in-discover/390038/8 "2026-09-03T13:14:15Z")

</div>

I can only see that its in the `traces-generic.otel-default` datastream. Not sure where I can see in which index it originally lands.

---

<div class="post-metadata">

**Author:** ![Jack\_Shirazi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_shirazi/32/91641_2.png) [@Jack\_Shirazi](https://discuss.elastic.co/u/Jack_Shirazi)\
**Post date:** [September 3, 2026, 5:16pm UTC](https://discuss.elastic.co/t/messaging-message-conversation-id-visible-in-traces-but-not-searchable-in-discover/390038/9 "2026-09-03T17:16:29Z")

</div>

and the earlier question?

Also what do you get in dev tools with

```auto
GET traces-generic.otel-default/_search
{
  "_source": true,
  "fields": [
    "attributes.messaging.message.conversation_id"
  ],
  "query": {
    "bool": {
      "filter": [
        { "term": { "trace_id": "YOUR_TRACE_ID" } },
        { "term": { "span_id": "YOUR_SPAN_ID" } }
      ]
    }
  }
}

```

---

<div class="post-metadata">

**Author:** ![ex.ko](https://avatars.discourse-cdn.com/v4/letter/e/90db22/32.png) [@ex.ko](https://discuss.elastic.co/u/ex.ko)\
**Post date:** [September 8, 2026, 10:50am UTC](https://discuss.elastic.co/t/messaging-message-conversation-id-visible-in-traces-but-not-searchable-in-discover/390038/10 "2026-09-08T10:50:29Z")

</div>

Sorry for the delayed answer.

I just checked for the fields you provided (`messaging.message.conversation_id` and `labels.messaging.message.conversation_id`) and I couldn't find any of those in the trace/span.

For the query I would need to ask our admin to do the query as I'm only a "user" on this Elastic platform. I'll give feedback as soon as I have something. Thanks again.
