Troubleshoot the EDOT Collector
Serverless Observability Stack
Use the topics in this section to troubleshoot issues with the EDOT Collector.
If you're sending EDOT SDK telemetry directly to APM Server's OTel intake, keep in mind that this flow is not supported. Send data to an EDOT Collector Gateway or Managed OTel intake instead.
If you're not sure where to start, review the Collector's logs for error messages and validate your configuration using the --dry-run option. For more detailed diagnostics, refer to Enable debug logging.
Collector out of memory: Diagnose and resolve out-of-memory issues in the EDOT Collector using Go's Performance Profiler.
Insufficient resources in Kubernetes: Troubleshoot resource allocation issues when running the EDOT Collector in Kubernetes environments.
Collector doesn't start: Resolve startup failures caused by invalid configuration, port conflicts, or missing components.
Missing or incomplete traces due to Collector sampling: Troubleshoot missing or incomplete traces caused by sampling configuration.
Collector doesn't propagate client metadata: Learn why the Collector doesn't extract custom attributes and how to propagate such values using EDOT SDKs.
- Export failures when sending telemetry data: Resolve export failures caused by
sending_queueoverflow and Elasticsearch exporter timeouts.
- Enable debug logging: Learn how to enable debug logging for the EDOT Collector in supported environments.
EDOT SDKs troubleshooting: For end-to-end issues that may involve both the Collector and SDKs.
Troubleshoot EDOT: Overview of all EDOT troubleshooting resources.
For in-depth details on troubleshooting, refer to the contrib OpenTelemetry Collector troubleshooting documentation.