Hi there, I'm exploring the capabilities of EDOT and I have an issue: Logs from my spring-boot app [otel.javaagent 2025-03-10 16:31:10:565 +0100] [OkHttp http://localhost:9200/...] WARN io.opentelemetry.exporter.internal.http.HttpExporter - Failed to export logs. Server responded with HTTP status…

Hi @yev Welcome to the community. And thanks for trying EDOT. Here are the current valid paths... this is for Java .. not all language SDK may support the APM Server path. JAVA App -> EDOT Java SDK OLTP exporter -> Elastic APM Server -> Elasticsearch JAVA App -> EDOT Java SDK OLTP exporter -> ED…

hi, @stephenb , thank your for your fast answer! I will try!

It is a fast moving time right now :slight_smile:

thank you @stephenb With otelcol-contrib docker I have successfully pushed the logs to my ES. But now I have another issue with metrics. I enabled metrics in oltp-collector config: service: pipelines: logs: receivers: [ otlp ] exporters: [ elasticsearch ] …

Opens a new topic with Proper Subject Line... I suspect there are some specific data type settings... that and I am not sure we support temporality yet.

Hello @stephenb I am a little bit confused about valid paths. This github doc indicates that APM Server should not be used in the guideline section: [image] That guide is correct? Thank you very much!

It is really just an artifact of how we see the future. I think our docs have shifted to actively discouraging sending OTel data through APM server and this is just a natural extension of that So yes, This should still be valid .. as part of a migration B) OTEL SDK (otlp) -> APM Server -> ECH (…

We have a self-managed Elasticsearch cluster so I understand we can use this path and is fully supported: JAVA App (tomcat) -> EDOT Java -> Elastic APM Server -> Self-Managed Elasticsearch On the other hand, with OTEL Collector (gateway mode) I understand that we should use exporters.elasticsearc…

Hi @adminunix I am not sure what the question is. Perhaps you should open a thread (working in an answered thread is not ideal) , with all the details,m Include the versions, etc and what you are trying to accomplish instead of piecemeal. There are many valid architectures it depends on what your…

The HTTP 400 Bad Request error occurs because the EDOT Java SDK cannot push OTLP data directly to the Elasticsearch port (9200), as Elasticsearch requires a specific translation layer to understand OpenTelemetry protocol buffers. To resolve this, you must route your traffic through either the Elasti…

[image] adminunix: JAVA App (tomcat) -> EDOT Java -> Elastic APM Server -> Self-Managed Elasticsearch Correct EDOT JAVA SDK can not write directly to Elasticsearch you need to either use a the APM Server or OTEL / EDOT Collector Here are all the permutations A) Legacy APM (v2) -> APM Serve…

EDOT pushing to elastic fails with HTTP status message: Bad Request

Elastic Observability

adminunix (Admin Unix) March 26, 2026, 2:32pm 13

Thank you very much Stephen!
I am ready to configure the agents after the info you provided.

Topic		Replies	Views
Elastic APM Not accessible outside docker container APM docker , nodejs , open-telemetry	9	2200	August 23, 2022
OTEL plugin error in sending data to APM server APM server , open-telemetry	6	3827	September 22, 2022
EDOT running in Gateway mode - "sending queue is full" Elastic Agent elastic-stack-monitoring	1	69	January 27, 2026
Error sending trace data to elasticsearch using otel collector Elasticsearch	0	318	April 30, 2024
Can not export traces from opentelemetry collector to APM Server: request to https://apm.<removed>:8200/v1/traces responded with HTTP Status Code 400 APM docker , open-telemetry	4	2050	September 27, 2022

EDOT pushing to elastic fails with HTTP status message: Bad Request

Related topics