Observability with Elasticsearch: Best Practices for High-Load Platform [ukr]
The session covers architectural strategies that keep Elasticsearch stable under heavy load: proper index and shard design, ILM policies, persistent queues in Logstash, metrics downsampling, and self-monitoring of the observability stack. Insights are drawn from operating platforms that handle terabytes of logs and millions of events per day.

Anton Pryhodko
EPAM, Systems Architect
- Systems Architect with 16+ years of experience in engineering and cloud infrastructure
- Expert in building observability stacks across AWS, Azure, GCP, and on-prem environments
- Co-organizer of mentoring programs on DevOps and Systems Engineering
- Experienced in implementing solutions based on Elastic Stack, Dynatrace, New Relic, and Grafana
- Conducts technical interviews for System/Cloud Architect/Engineer roles