Open Telemetry querying

Elastic search recommends against structuring data such that joins are needed for indexes, yet the OpenTelemetry data is put in multiple indexes. There's doesn't appear to be a way to configure the data to go to a single index. This seems to mean that some processing will have to be done outside of Kibana visualizations. One critical example: querying the original transactions that an error was for. I cant seem to find how that can be queried without pulling the data down and performing two queries local (one to get errors, then to query again using the from that other index).

Any examples of how to "join" the multiple open-telemetry indexes for querying stats like this?

Hi Kevin,

Welcome to the community! I've reclassified your query under Observability to make it easier to be picked up by those knowledgable about OTel. Can you confirm which version of Elastic you are using?

1 Like

Currently on 7.12, but will be doing an upgrade to 8.5 in about a month.

This issue is similar:

copy span context to error context · Issue #476 · elastic/apm-agent-rum-js (

Found it in this older post:

Errors not getting labels from spans - Elastic Observability / APM - Discuss the Elastic Stack

There does not seem to be any way to get the original transaction or span data without manually doing multiple queries outside of the Kibana/Elasticsearch query capabilities and joining the data.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.