Troubleshooting ES|QL
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. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. 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
Generally available
Stack
Generally available
This section provides some useful resource for troubleshooting ES|QL issues:
- The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability Preview since 9.4 This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. 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. Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability Unavailable This functionality is not available in Elastic Cloud Serverless. Query logging: Log all query types, including ES|QL, with a managed data stream (recommended)
- Legacy ES|QL query log: Log ES|QL queries using the older
esql.querylogsettings - Task management API: Learn how to diagnose issues like long-running queries.
- Circuit breaker settings: Learn how ES|QL uses the circuit breaker and how to configure it. For circuit breaker errors, see Circuit breaker errors.
For tips on writing efficient queries, refer to Optimize ES|QL query performance.
When filing a support case for a slow or failing ES|QL query, include the following information so the support team can investigate quickly:
- The full ES|QL query text
- The cluster version, available from
GET / - The index pattern and approximate document count
- The time range covered by the query
- The fields and field types across all indices participating in the query, available from the field capabilities API
- The
tookvalue from the response - Any error messages
- A query log entry, if query logging is enabled