Troubleshoot Elastic Distributions of OpenTelemetry (EDOT)

Serverless Observability Stack

Find solutions to common issues in EDOT components and SDKs.

Component troubleshooting

EDOT Collector troubleshooting: Troubleshoot issues with the EDOT Collector, including resource problems, configuration errors, and connectivity issues.
EDOT SDKs troubleshooting: Troubleshoot issues with EDOT SDKs for Android, .NET, iOS, Java, Node.js, PHP, and Python.

These guides apply to both the Collector and SDKs:

Connectivity issues: Resolve connection problems between EDOT components and Elastic, including firewall, proxy, and network configuration issues.
No data visible in Kibana: Diagnose why telemetry data (logs, metrics, traces) doesn't appear in Kibana after setting up EDOT.
429 errors when using the mOTLP endpoint: Resolve HTTP 429 Too Many Requests errors when sending data through the Elastic Cloud Managed OTLP endpoint.
Contact support: Learn how to contact Elastic Support and what information to include to help resolve issues faster.

EDOT SDKs are tested and supported only with EDOT Collector Gateway or Managed OTel intake. Using EDOT SDKs directly with APM Server's OTel intake is not supported.

Troubleshoot ingestion tools: Overview of troubleshooting for all ingestion tools, including EDOT, Logstash, Fleet, and Beats.
Elastic Support Portal: Access support cases, subscriptions, and licenses.
Elastic community forums: Get answers from experts in the community, including Elastic team members.