• Home
  • Extend
  • OpenTelemetry
  • OpenTelemetry Collector
  • Collector use cases
  • Transform OTLP gRPC

Transform OTLP gRPC

The following configuration example shows how you would configure a Collector instance to transform a gRPC OTLP request to its HTTP counterpart.

Demo configuration

yaml
receivers: otlp: protocols: grpc: exporters: otlphttp: endpoint: $DT_ENDPOINT/api/v2/otlp headers: Authorization: "Api-Token $DT_API_TOKEN" service: pipelines: traces: receivers: [otlp] exporters: [otlphttp] metrics: receivers: [otlp] exporters: [otlphttp] logs: receivers: [otlp] exporters: [otlphttp]

Prerequisites

  • At least Core distribution
  • The API URL of your Dynatrace environment
  • An API token with the relevant access scope

Components

For our configuration, we configure the following components.

Receiver

Under receivers, we specify the gRPC otlp receiver as active receiver component for our Collector instance.

Exporter

Under exporters, we specify the default otlphttp exporter and configure it with our Dynatrace API URL and the required authentication token.

For this purpose, we set the following two environment variables and reference them in the configuration values for endpoint and Authorization.

  • DT_ENDPOINT contains the base URL of your ActiveGate (for example, https://{your-environment-id}.live.dynatrace.com)
  • DT_API_TOKEN contains the API token

Service pipeline

Under service, we eventually assemble our receiver and exporter objects into pipelines, which explictly accept gRPC requests and forward them on HTTP to Dynatrace.

Related topics
  • Enrich ingested data with Dynatrace-specific dimensions

    Learn how to automatically enrich your telemetry data with Dynatrace-specific dimensions.

  • Enrich from Kubernetes

    Configure the OpenTelemetry Collector to enrich OTLP requests with Kubernetes data.