Digma Developer Guide
  • Welcome to the Digma Docs!
  • What is a Continuous Feedback platform?
  • Digma Quickstart
  • Installation
    • Local Install
      • Local Install Architecture
      • Installation Troubleshooting
    • Central (on-prem) Install
      • Resource Requirements
  • INSTRUMENTATION
    • Instrumenting your code for tracing
    • Java
      • Automatic Instrumentation in the IDE (IntelliJ)
      • Spring, Spring Boot, Dropwizard
        • Instrumenting your code in CI/Staging or the terminal
        • Instrumenting your application in Docker Compose
        • Instrumenting your application on Kubernetes
        • Covering more of your code with Observability
        • Using GitHub Actions (beta)
        • Using Micrometer Tracing (Spring Boot 3.x only)
        • Instrumenting code running in CLI
      • Quarkus, Micronaut, OpenLiberty
    • .NET
    • Correlating observability and source code commits
    • Sending Data to Digma using the OTEL Collector
    • Sending Data to Digma Using the Datadog agent
  • Use Cases
    • Design and write code more efficiently by understanding the system flows
    • Get early feedback on bottlenecks and code issues
    • Prioritize Technical Debt
  • Digma Core Concepts
    • Environments
    • Assets
    • Analytics vs. Issues
  • Digma Features
    • Issues
      • Suspected N+1
      • Excessive API calls (chatty API)
      • Bottleneck
      • Scaling Issue
      • Session In View Query Detected
      • Query Optimization Suggested
      • High number of queries
      • Slow Endpoint
    • Analytics
      • Top Usage
      • Request Breakdown
      • Duration
      • Code Nexus
      • Duration Breakdown
      • Endpoint Low/High Usage
    • Performance Impact
    • Test observability
    • Issue Criticality
  • Sample Projects
    • Spring Boot
  • Troubleshooting
    • Reporting Plugin Issues
    • Digma Overload Warning
Powered by GitBook
On this page
  • Set up Dual Shipping
  • Add tags to specify the Digma environment
  1. INSTRUMENTATION

Sending Data to Digma Using the Datadog agent

PreviousSending Data to Digma using the OTEL CollectorNextDesign and write code more efficiently by understanding the system flows

Last updated 10 days ago

Set up Dual Shipping

If you're using the Datadog Agent (dd-agent) and not an OTEL agent/collector, you can forward traces to Digma using Datadog's feature.

To use this feature, modify the agent's configuration to include Digma's DataDog receiver:

apm_config:
  additional_endpoints:
    "[REPLACE_WITH_DIGMAS_COLLECTOR_DATADOG_ENDPOINT]":
    - datadog_reciver

Alternatively, you can add the following env variable:

DD_APM_ADDITIONAL_ENDPOINTS={"[REPLACE_WITH_DIGMAS_COLLECTOR_DATADOG_ENDPOINT]": ["datadog_receiver"]}

Add tags to specify the Digma environment

Digma will automatically copy data from the Datadog traces such as the git commit hash, if present. However, to ensure the data is classified correctly within Digma, you need to add two additional tags to your tracing data. This can be done using environment variables.

export DD_TAGS=digma.environment:$ENV_NAME,digma.environment.type:Public

Additionally, to use custom instrumentation or Digma auto instrumentation, you can include the following environment variable that will configure the DD agent to respect the OTEL instrumentation attributes:

export DD_TRACE_OTEL_ENABLED=true

Alternatively,

dual shipping