Skip to main content

Dynatrace

Signals Provided
  • Metrics - Performance metrics from applications and infrastructure
  • Symptoms - Automatic symptom detection from metrics, traces, and external monitoring systems
  • Traces - Distributed traces for service dependency discovery and communication monitoring

Causely integrates with Dynatrace to ingest service dependencies and trace-based metrics, from both Kubernetes and ECS environments. This enables Causely to build a unified causal model across mixed container platforms and generate a dependency and service map that accurately reflects how your system behaves under change. By incorporating Dynatrace traces and service-level metrics, Causely strengthens reliability assurance across hybrid environments. The setup process below applies to both Kubernetes and ECS-based services.

Supported environments​

  • Kubernetes
  • ECS (via Dynatrace OneAgent / Dynatrace APM instrumentation)

Step 1: Create a user​

Create an API token for your Dynatrace account server.

Step 2: Create a Kubernetes Secret with the Dynatrace URL and API token​

After creating the API token create a Kubernetes Secret:

kubectl create secret generic \
  --namespace causely dynatrace-credentials \
  --from-literal=url="..." \
  --from-literal=api-token="..."

Step 3: Update Causely configuration​

Once the secret is created, update the Causely configuration to enable scraping for the dynatrace account. Enabling scraping allows Causely to ingest Dynatrace topology and telemetry for both Kubernetes and ECS services.

Below is an example configuration:

scrapers:
  dynatrace:
    enabled: true
    accounts:
      - secretName: dynatrace-credentials

Alternative: Enable Credentials Autodiscovery​

Causely supports credentials autodiscovery so you can add new accounts without editing config. Label the Kubernetes secret to enable autodiscovery for the Dynatrace scraper:

kubectl --namespace causely label secret dynatrace-credentials "causely.ai/scraper=Dynatrace"

Unified Stitching Across Kubernetes and ECS​

When Dynatrace is enabled, Causely automatically discovers and models dependencies between ECS and Kubernetes services, creating a unified causal view of your environment.

Causely will:

  • Discover and stitch dependencies across Kubernetes and ECS services, even when they span clusters or runtimes
  • Include service-level metrics (request rate, error rate, duration) and corresponding symptoms from ECS as part of the causal model
  • Display ECS services alongside Kubernetes services in Causely’s environment graph, dependency views, and reliability analysis