Troubleshooting the EDOT SDKs
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless Observability
Generally available
Stack
Generally available
Find solutions to common issues with EDOT SDKs for various programming languages and platforms.
Android SDK: Troubleshoot common problems affecting the Elastic Distribution of OpenTelemetry Android SDK.
Browser SDK: Troubleshoot common problems affecting the EDOT Browser SDK.
.NET SDK: Troubleshoot common problems affecting the EDOT .NET SDK.
iOS SDK: Troubleshoot common problems affecting the Elastic Distribution of OpenTelemetry iOS agent.
Java SDK: Troubleshoot common problems affecting the EDOT Java agent, including connectivity, agent identification, and debugging.
Node.js SDK: Troubleshoot issues using EDOT Node.js SDK.
PHP SDK: Troubleshoot issues using EDOT PHP agent.
Python SDK: Troubleshoot issues using EDOT Python agent.
These guides apply to all EDOT SDKs:
Enable debug logging: Learn how to enable debug logging for EDOT SDKs to troubleshoot application-level instrumentation issues.
No application-level telemetry visible in Kibana: Diagnose lack of telemetry flow due to issues with EDOT SDKs.
Proxy settings for EDOT SDKs: Configure proxy settings for EDOT SDKs when your application runs behind a proxy.
Missing or incomplete traces due to SDK sampling: Troubleshoot missing or incomplete traces caused by SDK-level sampling configuration.
Troubleshoot trace context header propagation: Troubleshoot missing or broken distributed traces when combining OpenTelemetry instrumentation with Elastic APM agents.
EDOT SDKs are tested and supported only with Elastic Agent Gateway or Managed OTel intake. Using EDOT SDKs directly with APM Server's OTel intake is not supported.
Elastic Agent troubleshooting: For end-to-end issues that may involve both the Collector and SDKs.
Troubleshoot Elastic OpenTelemetry: Overview of all Elastic OpenTelemetry troubleshooting resources.
Avoid using EDOT SDKs alongside any other APM agent, including Elastic APM agents. Running multiple agents in the same application process may lead to unexpected behavior, conflicting instrumentation, or duplicated telemetry.