Collector deployment
Deployment Options
The Collector can be deployed using a provided container image or directly with the published binary.
Kubernetes
For Kubernetes, the Dynatrace Collector can be deployed in the following ways:
OpenTelemetry Kubernetes Operator
Helm
Raw manifest
Dynatrace access details
Before you deploy the Collector, you need to set up the necessary Kubernetes secrets for the Dynatrace access details.
Use kubectl to create Kuberenetes secrets for the Dynatrace export details. Replace the placeholders with the actual values for the export URL and the API token.
kubectl create secret generic dynatrace-otelcol-dt-api-credentials --from-literal=DT_ENDPOINT=ACTIVEGATE_URL_HERE --from-literal=DT_API_TOKEN=API_TOKEN_HERE
The sample configurations apply a resource limit of 512 megabytes. You may need to adjust this under resources.limits.memory for your particular use case.
In Kubernetes, it is common to enrich OpenTelemetry signals using the Kubernetes Attributes processor. This requires a Kubernetes service account, which is automatically configured when using Operator or Helm.
For raw manifests, this needs to be configured manually by adding a spec.serviceAccountName: collector entry to the deployment manifest.
Manual deployment
To install the Collector binary manually
- Download the latest version for your operating system from GitHub.
Decompress the archive file.
Set up the desired configuration.
- Run the
dynatrace-otel-collectorbinary.
Deployment Modes
The Collector can be deployed as a standalone agent, a gateway, or a sidecar.
It's also possible to combine these deployment modes and chain Collector instances. Consider this if you are deploying the Collector in large environments.