Test your Grafana Loki knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
Why might a team choose to run Grafana, Loki, and Prometheus together as a unified observability stack rather than picking separate best-of-breed tools for metrics, logs, and dashboards from different vendors?
Questions in this quiz
Why might a team choose to run Grafana, Loki, and Prometheus together as a unified observability stack rather than picking separate best-of-breed tools for metrics, logs, and dashboards from different vendors?
What does horizontal scalability and high availability mean for a production Loki deployment, as opposed to running a single Loki instance?
Why does Loki's documentation commonly warn against using high-cardinality values (like a unique request ID or user ID) as labels?
What does Loki typically use as its underlying storage backend for the actual compressed log data (chunks)?
Why is Loki generally considered more cost-effective to operate at scale than a full-text-search-indexing log system like Elasticsearch?
What does it mean when Loki's design philosophy is sometimes summarized as "like Prometheus, but for logs"?
What is Promtail, and what role does it play in a typical Loki deployment?
What is a "log stream" in Loki's data model?
What is the practical purpose of retention/compaction policies in a Loki deployment?
What is a common reason a team already using Prometheus and Grafana for metrics might choose Loki specifically for logs, over a more general-purpose logging platform?
What is a common architectural pattern for scaling Loki's ingestion and query workloads independently, in larger production deployments?
Why is Loki often described as being "inspired by Prometheus"?