Loki is a horizontally scalable log system that indexes only labels (not the full log line), making it far cheaper than traditional log stores and a natural fit next to Prometheus and Grafana.
Why teams use it
- Low-cost logging by indexing labels instead of full text
- LogQL mirrors PromQL, so metrics and logs feel consistent
- Tight Grafana integration for correlated dashboards
Install it
docker run -d --name loki -p 3100:3100 grafana/loki:latest
docker run -d --name promtail -v $PWD/promtail.yaml:/etc/promtail/config.yml grafana/promtailA first working config
Promtail scraping local logs and shipping to Loki.
server: { http_listen_port: 9080 }
clients: [{ url: http://loki:3100/loki/api/v1/push }]
scrape_configs:
- job_name: system
static_configs:
- targets: [localhost]
labels: { job: varlogs, __path__: /var/log/*log }Run and verify
LogQL queries for filtering and metrics from logs.
{job="varlogs"} |= "error" | logfmt | status >= 500
# turn logs into a rate metric
sum(rate({app="web"} |= "panic" [5m]))Mistakes to avoid early
- High-cardinality labels (like request_id) destroying performance
- Pushing huge log volumes without retention or limits
- Expecting full-text indexing - Loki filters, it doesn't index content
Want senior help putting Grafana Loki to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.