# Dynatrace

### Description

This Dynatrace destination configures an OTLP exporter to send telemetry data (logs, metrics, traces) to a Dynatrace server for ingestion. It supports sending data to both SaaS and ActiveGate deployment types of Dynatrace.

### Supported Types

| Metrics | Logs | Traces | Bindplane Collector |
| ------- | ---- | ------ | ------------------- |
| ✓       | ✓    | ✓      | `v1.36.0`+          |

**Note for Metrics: Currently monotonic cumulative sums are not supported**

### Configuration

<table><thead><tr><th width="230.26171875">Field</th><th>Description</th></tr></thead><tbody><tr><td>Choose Telemetry Type</td><td>Select which types of telemetry to export (Logs, Metrics, Traces).</td></tr><tr><td>Deployment Type</td><td>Select the Dynatrace deployment type (SaaS or ActiveGate).</td></tr><tr><td>ActiveGate Hostname or IP</td><td>The hostname or IP address of your ActiveGate (required if Deployment Type is ActiveGate).</td></tr><tr><td>Port</td><td>The port to connect to. Default is 9999 for ActiveGate (required if Deployment Type is ActiveGate).</td></tr><tr><td>Environment ID</td><td>The Environment ID for your Dynatrace instance.</td></tr><tr><td>Dynatrace API Token</td><td>The API token used to authenticate with the Dynatrace API.</td></tr><tr><td>Skip TLS Certificate Verification</td><td>Enable to skip TLS certificate verification.</td></tr><tr><td>TLS Certificate Authority File</td><td>Certificate authority used to validate TLS certificates.</td></tr></tbody></table>

For more information on specific parameters, see [Dynatrace documentation](https://docs.dynatrace.com/docs/extend-dynatrace/opentelemetry/getting-started/otlp-export#export-with-otlp).

This destination supports the [retry settings](https://docs.bindplane.com/configuration/bindplane-otel-collector/retry-on-failure), the [sending queue settings](https://docs.bindplane.com/configuration/bindplane-otel-collector/sending-queue), and the [persistent queue settings.](https://docs.bindplane.com/configuration/bindplane-otel-collector/persistent-queue)

| Sending Queue | Persistent Queue | Retry on Failure |
| ------------- | ---------------- | ---------------- |
| ✓             | ✓                | ✓                |

### Example Configuration

For a basic configuration, specify the telemetry types to export, deployment type, environment ID, and API Token.

**Web Interface**

<figure><img src="https://1405008107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgmiOMzBfoNFwmKJFHMcJ%2Fuploads%2Fgit-blob-54e0426721623bd9a53e9df90701bdcccb49b79a%2Fintegrations-destinations-dynatrace-readme-image-1.png?alt=media" alt="Bindplane docs - Dynatrace - image 1"><figcaption></figcaption></figure>

**Standalone Destination**

```yaml
apiVersion: bindplane.observiq.com/v1
kind: Destination
metadata:
  id: dynatrace_otlp
  name: dynatrace_otlp
spec:
  type: dynatrace_otlp
  parameters:
    - name: telemetry_types
      value: ['Logs', 'Metrics', 'Traces']
    - name: deployment_type
      value: 'SaaS'
    - name: your_environment_id
      value: 'your_env_id'
    - name: dynatrace_api_token
      value: 'your_api_token'
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bindplane.com/integrations/destinations/dynatrace.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.