A Powerful Logs Management Solution We All Have and Use but...
summary
systemd-journal is presented as an underestimated, production-ready logs engine that indexes key=value fields, supports forward‑secure sealing for tamper detection, and scales with very low CPU and storage cost. Benchmarks claim 25–50k entries/core versus Loki ~5–10k and Elasticsearch ~2–5k; storage: Loki ~25% of raw, ES ~300%, journal ~200% (compressible to ~50%). Tools shown: log-to-journal, systemd-journal-upload/remote, journalctl, and Netdata UI; Netdata patches boost query speed ~14×, sampling after 1M entries, and cut a customer’s logging Opex from ~40% to ~5%.
AI-written summary · about
chapters (9)
- 0:00Logs management with systemd-journald
- 1:41Log management indexing
- 4:34Ingestion efficiency comparison
- 7:05Importing logs into journald
- 9:16Strengths and weaknesses
- 11:49Storing and securing logs
- 14:00Centralizing logs with journald
- 15:53Structured logs improvements
- 17:58N Dat’s log explorer optimizations
related talks
31mA powerful logs management solution we all have and use, but we underestimate
40mLarge-Scale Logging Made Easy
35mHow to Efficiently Manage Logs in Large-Scale Kubernetes Clusters
41mScaling Observability: From Chaos to Clarity with Open Source Tools
31mMy Logs Cost More Than My Services
30mCentralized Log Management
28mFrom Fragmented Logs to Unified Insights: Scaling O11y
46mConquering Distributed Cloud Logging Without Breaking the Bank