OpenTelemetry trace ingest API
The OpenTelemetry trace ingest API ingests OpenTelemetry traces to Dynatrace. Use this endpoint as a target for OpenTelemetry exporters.
The exporter can send data to one or more backends and is configured either as part of a collector in the collectors YAML file, or as a standalone service in your application's code.
Where to find the code:
- Collector: configure your exporter under the exporters section in the collector YAML file. Generally, various data sources are supported. Use OTLP to send data to Dynatrace.
- Code: where to put your exporter configuration differs from language to language. Go to OpenTelemetry traces and choose the language of your application from the menu to find the language-specific instructions.
The request consumes an
To execute this request, you need an access token with Ingest OpenTelemetry traces (
openTelemetryTrace.ingest) scope. To learn how to obtain and use it, see Tokens and authentication.
An ExportTraceServiceRequest message in binary protobuf format.
Request body objects
The object doesn't provide any parameters.
Request body JSON model
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
[ "string" ]
The request has been received and will be processed.
The request could not be processed. This may happen if the message is malformed.
The request could not be processed due to an internal server error.
The service is currently unavailable. This may happen if the module is paused.
- The search of traces/spans by OpenTelemetry resources attribute is limited to the service.name. Use the Service name filter on the Distributed traces page.
- The search of traces/spans by OpenTelemetry span attribute is limited to the span name. Use the Request filter on the Distributed traces page.