← Back to learning notes
Logstash and Elasticsearch architecture notes
A short checklist for ingestion-heavy Elastic stacks before performance issues become normal.
Review first #
- shard count versus actual data volume
- dynamic mapping growth
- expensive Logstash regex work
- bulk rejection and queue growth
- refresh behavior on hot indices
Reminder #
Heap pressure is often a symptom. Shard strategy, mapping control, and ingestion shape are usually the real architecture decisions.