← All insightsObservability

Monitoring and observability for Elasticsearch

Nir Geier, CodeWizard · 5 August 2025 · 3 min read · Intermediate

You cannot operate what you cannot see. Here is how to get useful signals out of Elasticsearch and turn them into alerts that mean something.

Elasticsearch is a distributed search and analytics engine built on Lucene, widely used for log analytics (the ELK/Elastic stack), full-text search and, increasingly, vector search.

What to watch

  • Define explicit mappings; disable dynamic where possible
  • Use Index Lifecycle Management for retention/rollover
  • Size shards deliberately (tens of GB each)
  • Track error rate and latency, not just up/down
  • Alert on symptoms tied to user impact

Operate and inspect

bash
curl -X POST localhost:9200/logs/_search -H 'Content-Type: application/json' -d '{
  "query": { "match": { "message": "timeout" } }
}'

Keep it healthy

  • Enable security (TLS + auth); never expose 9200 publicly
  • Use role-based access and API keys

Want senior help putting Elasticsearch to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult