Connect the Collector to OTLP Backends (Dynatrace, Datadog, Grafana)

Collector Output Configuration

Add an otel entry under the output section of your config.yaml:

output:
  otel:
    - name: "my-otel-backend"
      enabled: true
      endpoint: "https://your-otlp-endpoint/v1/logs"
      service_name: "ms-teams-agent"
      deployment_environment: "prod"
      headers:
        Authorization: "Bearer <token>"

Parameters

Parameter	Required	Description
name	Yes	Identifier for this OTLP output (used in logs)
enabled	Yes	Set to true to activate the OTLP output
endpoint	Yes	Full URL of the OTLP logs endpoint
service_name	No	Service name attached to exported logs
deployment_environment	No	Environment label attached to exported logs
headers	No	HTTP headers, usually used for authentication

Caution

Keep OTLP credentials out of version control. Use secure secret management for API keys and tokens.

Grafana OTLP Configuration

output:
  otel:
    - name: "grafana"
      enabled: true
      endpoint: "https://otlp-gateway-prod-eu-west-2.grafana.net/otlp/v1/logs"
      service_name: "ms-teams-agent"
      deployment_environment: "prod"
      headers:
        Authorization: "Basic <credentials>"

Detailed setup: OTLP to Grafana Cloud.

Datadog OTLP Configuration

output:
  otel:
    - name: "datadog"
      enabled: true
      endpoint: "https://otlp.datadoghq.com/v1/logs"
      service_name: "ms-teams-agent"
      deployment_environment: "prod"
      headers:
        DD-API-KEY: "<api-key>"

Detailed setup: OTLP to Datadog.

Dynatrace OTLP Configuration

output:
  otel:
    - name: "dynatrace"
      enabled: true
      endpoint: "https://{your-tenant}.live.dynatrace.com/api/v2/otlp/v1/logs"
      service_name: "ms-teams-agent"
      deployment_environment: "prod"
      headers:
        Authorization: "Api-token <token>"

Note

Dynatrace can be configured either with native output.dynatrace or via output.otel when your architecture is OTLP-first.

Validate the Connection

After editing the configuration, run:

ms-teams-agent validate --config ./config.yaml
ms-teams-agent test-connection --config ./config.yaml
ms-teams-agent run --config ./config.yaml --dry-run

Verify Data Arrival

1. Grafana: confirm logs are visible in your logs data source and filter on service_name.
2. Datadog: confirm logs arrive in Log Explorer and contain Teams event families.
3. Dynatrace OTLP: confirm logs arrive in Logs/Grail with expected source fields.
4. If data is not arriving, check collector logs and then follow Collector Troubleshooting.

✅ Success criteria:

• Collector logs confirm OTLP export with no errors
• Your OTLP platform shows logs from service_name = "ms-teams-agent"
• Event families (MSTeams_CallRecords_*) are visible in the platform

❌ If this fails:

• Re-run validate and test-connection
• Verify OTLP endpoint URL and authentication headers
• Collector Troubleshooting