You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We will piggyback on the work done for #3984 to serve on the same port as used for receiving data from Elastic APM agents. Initially we will support OTLP/gRPC, later we can consider extending this to OTLP/HTTP.
The APM Server must be capable of receiving at least traces and metrics over OTLP, as we do with the elastic opentelemetry-collector exporter and we should also consider extending this to receiving logs.
The text was updated successfully, but these errors were encountered:
I think we're going to have to vendor go.opentelemetry.io/collector in the apm-server tree, renaming the packages (e.g. apm-server/internal/otel_collector/...). The gRPC services are all hidden in internal packages (go.opentelemetry.io/collector/internal/data/...).
Add native OpenTelemetry Protocol (OTLP) intake support to APM Server.
We will piggyback on the work done for #3984 to serve on the same port as used for receiving data from Elastic APM agents. Initially we will support OTLP/gRPC, later we can consider extending this to OTLP/HTTP.
The APM Server must be capable of receiving at least traces and metrics over OTLP, as we do with the elastic opentelemetry-collector exporter and we should also consider extending this to receiving logs.
The text was updated successfully, but these errors were encountered: