AutoGineer
Generated banner for Elasticsearch Query Optimization
Generated logo for Elasticsearch Query Optimization

Elasticsearch Query Optimization

ElasticOfficialCreated by elastic

  • Skill
  • Workflow
  • Software development
  • Apache-2.0
  • No issues found
Download ZIP

From the author

Diagnose slow Elasticsearch Query DSL searches and propose measured fixes. Use when a search is slow, profile output shows an expensive clause, exact-match filters sit in scoring context, or leading wildcards dominate latency. Ground every recommendation in search profiling — move non-scoring clauses to filter context, eliminate leading wildcards, and re-profile to confirm improvement.
— the description by elastic

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured methodology for identifying and resolving performance bottlenecks in Elasticsearch queries. By leveraging the search profiling API, users can move beyond guesswork to identify expensive query clauses, such as unnecessary scoring filters or inefficient leading wildcards. The workflow emphasizes data-driven optimization, requiring users to profile the baseline, implement targeted rewrites—such as moving clauses to filter context—and re-profile to verify performance gains.

What it does

  • Diagnoses slow Query DSL performance using the Elasticsearch profiling API.
  • Identifies expensive clauses like leading wildcards or unnecessary scoring filters.
  • Provides patterns for moving exact-match clauses from must to filter context.
  • Offers strategies to replace inefficient leading wildcards with optimized alternatives.
  • Validates query rewrites using the validate-query API.
  • Requires measured before-and-after comparisons to confirm optimization success.

When to use it

  • When a search query is performing slowly and requires optimization.
  • When profile output indicates expensive clauses dominating query latency.
  • When exact-match filters are incorrectly placed in the scoring context.
  • When leading wildcards are causing high latency due to full-term scans.

Advantages

  • Grounds all optimization recommendations in objective profiling data.
  • Improves performance by leveraging the filter cache for exact-match clauses.
  • Reduces query latency by eliminating inefficient wildcard scanning.
  • Preserves search semantics while optimizing execution efficiency.

Usage examples

“My search is slow, how do I optimize it?”
The agent will guide you through running a profiled search, identifying the top-cost collector in the profile tree, and rewriting the query to move non-scoring filters to the filter context.
“Why is my wildcard query taking 5 seconds?”
The agent will analyze the profile to confirm if a leading wildcard is causing a full-term scan, then suggest replacing it with a match or match_phrase query on an analyzed field.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/elastic/elasticsearch-query-optimization/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip elasticsearch-query-optimization.zip -d .agents/skills

Documentation by elastic

Elasticsearch Query DSL Optimization

Diagnose why a Query DSL search is slow, identify the dominant cost from the profile (not guesswork), rewrite the query to remove that cost while preserving match semantics, and re-measure with profiling enabled.

<!-- begin-partial: preamble -->

Environment Configuration

This skill executes Elasticsearch operations through the elastic CLI. If the elastic CLI is not installed, tell the user what it is needed for. Do not guess credentials, call the HTTP API directly, or attempt other workarounds.

This skill references operations in HTTP-shorthand form (e.g., GET /, GET /_cat/indices, GET /{index}/_mapping, GET /{index}/_settings/index.mode, POST /_query). The Operations table at the end of this document maps each shorthand to the equivalent elastic CLI command — always use the CLI rather than calling the HTTP API directly.

<!-- end-partial: preamble -->

Scope: Query DSL searches via POST /{index}/_search. This skill does not migrate queries to ES|QL — it optimizes the existing bool/match/term/wildcard structure the user already runs.

Ground rule: Never recommend "add shards" or "scale hardware" as the primary fix when the profile names a specific clause (for example WildcardQuery at ~3.8s). Fix the query first; infrastructure changes require evidence the query is already optimal.

Process

  1. Confirm connectivity and locate the target index. Call GET /. If the call fails, stop — do not guess endpoints or credentials. When the user names an index pattern (for example logs-*), narrow candidates with GET /_cat/indices and pick the index or pattern the query actually targets.

    Decision: proceed only when the index is known. Data needed: index name or pattern, and the slow Query DSL body (from the user or from a saved search).

  2. Profile the slow query to find the dominant cost. Call POST /{index}/_search with "profile": true and the user's query unchanged. Read took, then inspect profile.shards[].searches[].query — sort child collectors by time_in_nanos and identify the top contributor.

    Decision: classify the bottleneck from profile evidence:

    • TermQuery / PointRangeQuery / MatchNoDocsQuery inside must alongside a scoring clause — exact-match or range filters are being scored unnecessarily. Likely fix: move them to filter context (step 4a).

    • WildcardQuery with a leading * (for example message:*timeout*) — cannot use the inverted index; scans terms per document. Likely fix: remove the leading wildcard (step 4b).

    • MatchQuery on a text field — expected scoring cost; optimize only if profile shows it dominates after filter-context fixes.

    • High aggregation time — separate from query tuning; profile the agg tree (out of scope unless the user asked about aggs).

    Data needed: profile tree with type, description, time_in_nanos, and breakdown (especially next_doc for wildcards). Quote the top contributor verbatim when explaining the diagnosis.

  3. Inspect field mappings before rewriting. Call GET /{index}/_mapping. For every clause you will move or rewrite, confirm the field type:

    • term / terms / filter on exact values — field must be keyword (or another non-analyzed type). A term on a text field is a common bug; if types are wrong, say so and suggest the correct sub-field (for example service.keyword) or a mapping change — do not silently rewrite.

    • match / match_phrase — target a text field (analyzed).

    • wildcard — works on keyword or wildcard types; leading * still forces a scan regardless of type.

    Decision: only propose rewrites that match confirmed types. Data needed: mapping for each field referenced in the query.

  4. Rewrite the query to remove the profiled bottleneck.

    4a. Move non-scoring clauses from must to filter

    When exact-match term/terms/range/match on a keyword (or other non-scoring intent) clauses sit in must alongside a full-text match that should drive relevance:

    • Move exact-match clauses into bool.filter (or a filter array entry).

    • Keep only clauses that must affect _score in bool.must (typically the full-text match).

    Why: filter context skips scoring and participates in the filter/bitset cache on repeated queries. Semantics: the same documents match; only scoring and performance change — state this explicitly.

    Example rewrite pattern:

    {
  "query": {
    "bool": {
      "filter": [{ "term": { "status": "active" } }, { "term": { "tenant_id": "acme" } }],
      "must": [{ "match": { "description": "wireless keyboard" } }]
    }
  }
}
    4b. Eliminate leading wildcards

    When the profile shows WildcardQuery with description like message:*timeout* and high next_doc time, the leading * prevents index lookup. Choose a fix based on mapping and user intent (substring vs prefix vs exact):

    IntentPreferred rewrite
    Full-text substring in logsmatch or match_phrase on the analyzed message text field
    Literal substring on keywordwildcard-typed field, or reindex with ngram analyzer
    Prefix only (timeout*)prefix query on keyword, or edge ngram at index time

    Also move any non-scoring exact match (for example { "match": { "service": "checkout" } } on a keyword) into filter — use term on the keyword field when the mapping confirms it.

    Example rewrite pattern:

    {
  "query": {
    "bool": {
      "filter": [{ "term": { "service.keyword": "checkout" } }],
      "must": [{ "match": { "message": "timeout" } }]
    }
  }
}

    Adjust field names (service vs service.keyword) to match the mapping from step 3.

    4c. Optional — validate rewrite before profiling

    When semantics are uncertain (for example changing wildcard to match may include analyzed tokens the wildcard excluded), call POST /{index}/_validate/query?explain=true with the rewritten query and read the explanation for obvious mismatches.

    Decision: pick the smallest rewrite that addresses the profiled cost. Data needed: rewritten Query DSL body.

  5. Re-profile the rewritten query and compare. Call POST /{index}/_search again with "profile": true and the rewritten query. Compare took and the top profile collector to the baseline from step 2.

    Decision: report success only when the dominant collector changed or time_in_nanos dropped materially. If the profile still shows a leading wildcard or scored filters, iterate — do not declare victory from took alone without profile confirmation.

    Data needed: before/after profile summaries (top collector type, description, time_in_nanos).

  6. Report findings in this order.

    1. Root cause — quote the profile (for example "WildcardQuery message:*timeout* ≈ 3.8s, mostly next_doc").

    2. Rewrite — show the optimized bool structure with filter vs must separation.

    3. Mapping notes — keyword vs text confirmations from GET /{index}/_mapping.

    4. Measured improvement — before/after profile or took from step 5.

    5. Semantic caveat — only if the rewrite could change which documents match (for example match vs substring wildcard).

Guidelines

  • Profile first. If the user supplies a profile summary, use it — but still recommend re-profiling after changes.

  • Filter is for equality, must is for relevance. Status, tenant ID, service name, and time ranges rarely belong in must when a text query drives ranking.

  • Leading wildcards are almost never the right fix for log search. Prefer analyzed match/match_phrase; reserve wildcard for suffix patterns (timeout*) on keyword or wildcard-typed fields.

  • Do not conflate slow with wrong. A slow query can return correct results; optimization preserves the result set unless you explicitly warn about a semantic trade-off.

  • Deep reference: profile collector types, filter-cache behavior, and wildcard alternatives — references/query-optimization-reference.md.

Examples

Unscored terms in must

Input: bool.must contains term on status, term on tenant_id, and match on description.

Diagnosis: profile shows scored TermQuery collectors alongside MatchQuery; exact filters do not need scoring.

Fix: move both term clauses to filter; keep match in must. Confirm status and tenant_id are keyword.

Leading wildcard dominates latency

Input: wildcard message:*timeout* plus match on service in must. Profile: WildcardQuery ~3.8s.

Diagnosis: leading * forces term enumeration; not an index/shard problem.

Fix: match on analyzed message; move service to filter as term on keyword. Re-profile — expect WildcardQuery to disappear or shrink to negligible time.

Operations

HTTP API (shorthand)elastic CLI command
GET /elastic es info
GET /_cat/indiceselastic es cat indices --index '<pattern>'
GET /{index}/_mappingelastic es indices get-mapping --index '<index>'
POST /{index}/_searchelastic es search --index '<index>' --input-file '<search-body.json>'
POST /{index}/_validate/query?explain=trueelastic es indices validate-query --index '<index>' --explain true --query '<json>'

Include "profile": true in the search JSON body (or pass --profile true) when profiling in steps 2 and 5.

Files

LICENSE

                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright 2026 Elasticsearch BV

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

The author says: Elasticsearch 8.x or 9.x, self-managed, Elastic Cloud Hosted, or Elastic Cloud Serverless; relies on the search profiling API available on all deployment types. Requires the `elastic` CLI ≥ 0.2 with `stack es` support.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
elastic
Publisher
Elastic (Official)
Source
elastic/agent-skills · skills/elasticsearch/elasticsearch-query-optimization · commit 09d879d
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Also distributed in
elastic/agent-skills

AutoGineer is not affiliated with or endorsed by elastic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download elasticsearch-query-optimization.zip