Operations report: Running Loki on Different On-Prem Environments
summary
Red Hat migrates Elasticsearch-based OpenShift logging to Loki using an in-cluster Loki Operator, already deployed to over 1,000 clusters; predefined sizes extra small small medium map to expected ingest rates and support horizontal scaling for spikes. Operator removes external datastores, standardizes on object storage with boltDB shipper and tsdb shipper, simplifies a thousand+ config knobs to a compact LokiStack CR, targets short-term retention (typical ≤30 days), and ships dashboards, alerts, and playbooks for debugging and upgrades.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:52What do we do?
- 1:58What brought us here?
- 3:29Why did we choose Loki?
- 4:35What did we do with the operator?
- 6:26How we picked pre-defined sizes
- 8:10Zero dependencies: simpler setup and easier debugging
- 10:35Limits, storage, and retention
related talks
31mLoki: Like Prometheus But for Logs
25mLoki: Prometheus-inspired logging for cloud native
05mGrafana Loki Log Aggregation for Incident Investigations
44mIntroduction to Grafana Loki
37mGrafana Loki: Like Prometheus, But for logs.
35mFrom New Cluster to Insight. Deploying Monitoring and Logging to Kubernetes
53mGetting started with Grafana Loki, a modern logs database
01h 02mHow companies use LOKI to run their business