Connect the Collector to Dynatrace

Collector Output Configuration

Add a dynatrace entry under the output section of your config.yaml:

output:
  dynatrace:
    enabled: true
    dynatrace_tenant_id: "your-dynatrace-tenant-id"
    dynatrace_api_token: "your-logs-ingest-token"

Parameters

Parameter	Required	Description
enabled	Yes	Set to true to activate the Dynatrace output
dynatrace_tenant_id	Yes	Your Dynatrace SaaS tenant ID (e.g. abc12345)
dynatrace_api_token	Yes	API token with logs.ingest scope

Caution

Protect your API token — use file permissions and avoid committing it to version control. Store the config file at a path accessible only by the collector service account.

Optional: Time Format

You can configure the timestamp format for log records sent to Dynatrace:

output:
  dynatrace:
    enabled: true
    dynatrace_tenant_id: "your-tenant-id"
    dynatrace_api_token: "your-token"
    time_fields_format: "iso8601"

Supported values: epoch_ms (default), epoch_s, epoch_ns, iso8601, rfc3339.

Test the Connection

After editing the configuration, run one first cycle:

./ms-teams-agent.bin --config ./conf/config.yaml --ignore_state

Then check collector logs to confirm Graph authentication and Dynatrace export are successful.

Verify Data Arrival

After a successful first collection cycle:

1. In Dynatrace, open Logs and filter by log.source = "MSTeams_CallRecords_CallMetadata".
2. Confirm records are arriving in the ms_teams bucket.
3. Open the MS Teams Observability app — the Overview page should show live data.

If data is not arriving, see Troubleshooting.