Troubleshooting the EDOT SDKs
Serverless Observability Stack
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.
.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.
EDOT Collector troubleshooting: For end-to-end issues that may involve both the Collector and SDKs.
Troubleshoot EDOT: Overview of all EDOT 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.