if the log is sent from an OpenTelemetry agent to the APM Server, APM Server will translate the root span or certain kinds of spans as a transaction when receiving otel data so that the logs will contain the transaction ID which can be the same as the root span ID.
We are using OpenTelemetry for the sending metrics and traces to the monitoring backend. The logs are sent via Filebeat.
In detail, we use the span and trace id from the OpenTelemetry agent and build (together with other log relevant information) a structured log (JSON) that is sent to the monitoring backend.
So sorry for getting back to you so late.
Yes OpenTelemetry logging integration with Elastic Observability is in preview state indeed.
We are using OpenTelemetry for the sending metrics and traces to the monitoring backend. The logs are sent via Filebeat.
In detail, we use the span and trace id from the OpenTelemetry agent and build (together with other log relevant information) a structured log (JSON) that is sent to the monitoring backend.
We don't have support for that yet, but you might want to try duplicating every id in the log and set it as both a transaction and span ID. I have not tried it on my side so it might not work and the UI could break, that's what we can suggest right now. Apologies for not being super helpful. I will deliver this case to our product team.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.