elasticsearch-best-practices

Apply Elasticsearch indexing, mapping, and query best practices for performance.

Updated Jul 12, 2025
One-click install
npx skills add https://github.com/contatomaycon/underchat --skill elasticsearch-best-practices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elasticsearch-best-practices
Source: https://github.com/contatomaycon/underchat/tree/main/.agents/skills/elasticsearch-best-practices
Command: npx skills add https://github.com/contatomaycon/underchat --skill elasticsearch-best-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Elasticsearch development best practices address inefficiencies in indexing, mapping, and query design, helping teams build scalable, fast search experiences.

Core Features & Use Cases

  • Design indices and mappings based on query patterns to improve relevance and performance
  • Tune analyzers, tokenization, and search settings to optimize queries
  • Implement shard sizing, ILM, and security controls for scalable, secure deployment
  • Monitor cluster health and optimize queries for typical production workloads

Quick Start

Audit your existing indices for explicit mappings and begin tuning settings for common query workloads.

Frequently Asked Questions about elasticsearch-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve Elasticsearch performance for slow indexing and search queries?

To improve Elasticsearch performance, apply proven indexing practices by designing indices with explicit mappings, tuning analyzers, and choosing appropriate field types based on your query patterns to optimize relevance and speed.

What is the best way to design Elasticsearch mappings for typical search workloads?

Designing Elasticsearch mappings involves defining explicit field types and tuning tokenization settings to match your query patterns, which ensures maintainable query structures and optimal search relevance for typical workloads.

How do I size shards and configure ILM for a scalable Elasticsearch cluster?

Sizing shards and configuring Index Lifecycle Management (ILM) involves tuning index settings and implementing security controls to maintain cluster health and ensure scalable, secure deployments across production workloads.

Why does Elasticsearch cluster health degrade under heavy query workloads?

Elasticsearch cluster health degrades when indices lack explicit mappings or have poorly tuned analyzers, causing inefficient queries; monitoring cluster health and optimizing query patterns resolves these typical production bottlenecks.

Do I need explicit mappings for every Elasticsearch index?

Explicit mappings are required for Elasticsearch indices to enforce appropriate field types, tune analyzers accurately, and maintain query relevance, preventing dynamic mapping issues that degrade performance and cluster stability.

Can I tune Elasticsearch analyzers and tokenization without changing my existing indices?

Tuning Elasticsearch analyzers and tokenization requires updating index settings and mappings, meaning you must audit existing indices and apply proven best practices to optimize queries for typical search workloads.