You Can't Just Send All Logs to Elastic
summary
The talk explains why sending all application logs to Elasticsearch is not as straightforward as it seems, focusing on Elasticsearch’s characteristics for log storage, pitfalls of Java clients and other clients, and related engineering anti-patterns. It covers practical issues with using Elasticsearch for logs, high-load considerations, and best-practice recommendations.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:29Why not send all logs to Elastic
- 3:35Elastic for logs vs text search
- 6:04Index separation in Elastic
- 7:47Making Elastic user-friendly
- 9:12Log structure and field issues
- 10:56Field limit in Elastic
- 12:20Elastic REST client
- 17:14Elastic version upgrade pitfalls
- 20:52Client errors and failover
- 23:23Apache HTTP client issues
- 24:07Cluster topology updates
- 28:24Data compression for Elastic
- 29:28Apache HTTP client settings
- 32:00Client settings summary
- 33:02High Level client pros and cons
- 34:28Bulk indexing in Elastic
- 37:58Idempotency and unique IDs
- 41:04Document indexing performance
- 42:48Optimal bulk request size
- 44:12Bulk request error handling
- 45:37Elastic exception analysis
- 47:24Talk summary
- 49:09Q&A
related talks
54m7 Petabytes of Logs in Elastic. How We Did It
42mMake your logs work for you
31mFast logs
47mGraylog: one tool to log 'em all
49mElasticsearch, Logstash & Kibana
40mBuilding Observability with Elasticsearch: Practices for High Load
25mOne Size Does Not Fit All: A Polystore Architecture for Logs and Traces
54mScale Elasticsearch for Your Java Applications. Philipp Krenn. Java Fest 2020 Online
