Datadog APM Traces Not Showing Up

How to fix it

Try these in order — the most common fix is first.

1. 1. Verify Agent reachability

   Copy steps
   1. Ensure the Agent is running with APM enabled
   2. Check DD_AGENT_HOST and port 8126 from the app
   Did this fix it? Yes No

2. 2. Enable tracer debug logs

   Copy steps
   1. Set DD_TRACE_DEBUG=true
   2. Look for send errors beside app logs
   Did this fix it? Yes No

3. 3. Set unified service tags

   Copy steps
   1. Set DD_SERVICE, DD_ENV, DD_VERSION
   2. Look under the integration name (e.g. flask) if unset
   Did this fix it? Yes No

4. 4. Unify split services

   1. Use DD_SERVICE_MAPPING to rename integration service names
   Did this fix it? Yes No

Symptoms

No traces or the service is missing in APM or Software Catalog.

Why it happens

• Tracer cannot reach the Agent
• Port 8126 conflict
• Service tag not set so traces appear under integration name
• Agent trace limits

This guide also covers

• datadog apm traces not showing
• datadog service not showing apm
• datadog trace missing

Other Datadog errors

• How to Cancel Datadog Subscription
• Datadog Agent Not Reporting Metrics or Host Missing
• Datadog Duplicate Hosts After AWS Integration
• Datadog Logs Not Showing in Log Explorer
• Datadog Agent High CPU or Memory Usage
• Datadog Monitor No Data Alerts Not Working
• Why Is My Datadog Bill So High: Custom Metrics
• Datadog Agent 403 API Key Invalid in Kubernetes