Preparing for a DevOps interview that covers Grafana Loki? These questions come up again and again - here are strong, concrete answers.
Q: What is Grafana Loki and why use it?
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.
- 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
Q: What are the best practices you follow?
- Keep labels low-cardinality; filter within the stream using LogQL
- Set per-tenant retention and ingestion limits
- Structure logs (logfmt/JSON) so LogQL parsers work well
Q: What mistakes have you seen?
- 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
Q: Show a basic configuration
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 }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.