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
  • If you're using an OpenTelemetry Collector
  1. INSTRUMENTATION

Sending Data to Digma using the OTEL Collector

If you’re already using OpenTelemetry (OTEL), integrating with Digma is seamless—Digma provides an OTEL receiver, so you only need to configure your system to export tracing data.

Not using OTEL yet? No worries! Setting up OTEL instrumentation is straightforward in most programming languages, often requiring little to no code changes. Plus, Digma offers enhanced observability support for certain languages, enabling deeper tracing even if traceability wasn’t originally part of your design.

If you're using an OpenTelemetry Collector

  1. Add an OTLP exporter and supply the Digma URL (ingress DNS or IP) for the otel-collector service. See the Central (on-prem) Install page for more details.

# collector-config.yaml

receivers:
# ...
exporters:

  #... other exporters
  
  otlp/digma:
    endpoint: ${DIGMA_COLLECTOR_URL}
    tls:
      insecure: true
  1. Update your observability pipeline to include sending traces to the Digma receiver as well:

# collector-config.yaml

receivers:
# ..  
exporters:
# ..  
service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [OTHER_EXPORTERS,otlp/digma]
      processors: [batch]

PreviousCorrelating observability and source code commitsNextSending Data to Digma Using the Datadog agent

Last updated 1 month ago