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
      • Sending Data to Digma Using the Datadog agent
    • .NET
    • Correlating observability and source code commits
    • Sending Data to Digma using the OTEL Collector
  • 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
  • Automatic Code Instrumentation
  • Optional Context for Better Errors Processing
  • Sample project
  1. INSTRUMENTATION

.NET

PreviousSending Data to Digma Using the Datadog agentNextCorrelating observability and source code commits

Last updated 10 days ago

Digma works well with zero code instrumentation and the more traditional manual instrumentation configuration.

Automatic Code Instrumentation

TBD

Optional Context for Better Errors Processing

For better parsing of .NET errors and to differentiate between external code and your application, it is recommended to add the code.namespace.rootattribute. The easiest way to add that attribute is via the OTEL_RESOURCE_ATTRIBUTES environment variable. 

export OTEL_RESOURCE_ATTRIBUTES=[...existing values],code.namespace.root=YOUR_APP_NAMESPACE

Sample project

LogoGitHub - digma-ai/otel-sample-application-dotnet: Example .NET 6.0 ASP.NET MVC CORE API application with OpenTelemetry istrumented for reference and testing purposesGitHub