Most Elasticsearch pain is self-inflicted and predictable. Here are the mistakes we see most, and the fix for each.
Mistake 1: Unbounded mapping explosion from dynamic fields
Fix: Define explicit mappings; disable dynamic where possible. Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.
Mistake 2: Too many small shards hurting performance
Fix: Use Index Lifecycle Management for retention/rollover. Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.
Mistake 3: No ILM, so indices grow without retention
Fix: Size shards deliberately (tens of GB each). Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.
A safer baseline
Create an index with an explicit mapping.
curl -X PUT localhost:9200/logs -H 'Content-Type: application/json' -d '{
"mappings": { "properties": {
"@timestamp": { "type": "date" },
"level": { "type": "keyword" },
"message": { "type": "text" }
} }
}'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.