Hi, We have our application instrumented to push traces on otlp to open telemetry collector and we are then exporting traces to elastic APM. we were earlier using "elastic" exporter to push traces to elastic APM server directly and it was working perfectly fine until it was deprecated and we are fo…

[image] ramdas: as per latest documentation, we are now trying to use otlp or otlphttp exporter in our opentelemetry collector, however it is not working. latest status is we are getting HTTP 400 while using otlphttp exporter. It appears that we're not handling the otel-collector's default co…

Can not export traces from opentelemetry collector to APM Server: request to https://apm.<removed>:8200/v1/traces responded with HTTP Status Code 400

Elastic Observability APM

axw (Andrew Wilkins) September 5, 2022, 2:45am 3

It appears that we're not handling the otel-collector's default compression properly: OTLP/HTTP requests fail on compressed payloads · Issue #9036 · elastic/apm-server · GitHub

Until that is fixed, you can work around this by adding compression: none in the otlphttp config block.

1 Like

Topic		Replies	Views
OTEL plugin error in sending data to APM server APM server , open-telemetry	6	3762	September 22, 2022
404 error while pushing traces from OTel Exporter to APM server APM go , server , open-telemetry	15	8049	November 15, 2022
Elastic APM Not accessible outside docker container APM docker , nodejs , open-telemetry	9	2170	August 23, 2022
Failed to push trace data via OTLP exporter: rpc error: code = Unavailable desc = connection closed APM open-telemetry	2	3939	October 28, 2021
How does the "jaeger client" data access "APM" via "OpenTelemetry"? APM docker , go , server	3	1677	August 5, 2021

Can not export traces from opentelemetry collector to APM Server: request to https://apm.<removed>:8200/v1/traces responded with HTTP Status Code 400

Related topics