Building Observability with Elasticsearch: Practices for High Load
summary
Practical guidance for running Elasticsearch as an observability backend under high load, covering index and shard layout, ILM (index lifecycle management) policies, Logstash persistent queues, metric downsampling, and monitoring the observability system itself. Shares real-world experience operating a platform handling terabytes of logs and millions of events per day.
AI-written summary · about
chapters (19)
- 0:00Monitoring problems
- 2:14Unified observability platform
- 5:32Logstash queue data loss
- 8:47Queue settings and space
- 10:16Heap memory instability
- 11:21Index design and shards
- 14:16Dynamic mapping effects
- 16:48Index naming standards
- 19:23Kibana dashboard benefits
- 20:29Hot/cold/frozen tiers
- 23:00Metric downsampling savings
- 24:49Data retention monitoring
- 27:00Observability for platform
- 28:44Critical Elastic metrics
- 31:15Platform building advice
- 33:04Q&A: field mapping
- 35:34Q&A: CPU and RAM
- 36:40Q&A: Logstash config
- 38:52Q&A: field deprecation
related talks
10mEffective Observability: Best Practices with Elastic
41mScaling Observability: From Chaos to Clarity with Open Source Tools
44mSurviving Elasticsearch
29mHow (not) to Scale Elasticsearch for Data Analytics!
01h 01mBest Practices With Elasticsearch
24mOperating at scale with Elastic Search in production
52mGrowing to full-suite observability with Elasticsearch & the ELK Stack (PRT267)
10mWhy your observability is costing you too much?
