Troubleshoot the Elastic Agent
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
Use the topics in this section to troubleshoot issues with the Elastic Agent.
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 Elastic Agent using Go's Performance Profiler.
Insufficient resources in Kubernetes: Troubleshoot resource allocation issues when running the Elastic Agent 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.
APM services missing due to misconfigured elasticapm connector: Resolve missing APM services and metrics caused by placing the
elasticapmconnector underprocessors:instead ofconnectors:.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.ResourceExhaustederrors and decompression limits in Collector-to-Collector pipelines: TroubleshootResourceExhaustederrors caused by gRPC message size limits, decompression limits, memory pressure, or backpressure in Collector-to-Collector pipelines.
- Enable debug logging: Learn how to enable debug logging for the Elastic Agent in supported environments.
EDOT SDKs troubleshooting: For end-to-end issues that may involve both the Collector and SDKs.
Troubleshoot Elastic OpenTelemetry: Overview of all Elastic OpenTelemetry troubleshooting resources.
For in-depth details on troubleshooting, refer to the contrib OpenTelemetry Collector troubleshooting documentation.