Project: Grafana Loki (Observability and Analysis / Observability)
File: overview.md

menuTitle: Loki overview title: Loki overview description: Loki product overview and features. weight: 200 aliases: ../overview/ ../fundamentals/overview/ Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by . Loki differs from Prometheus by focusing on logs instead of metrics, and collecting logs via push, instead of pull. Loki is designed to be very cost effective and highly scalable. Unlike other logging systems, Loki does not index the contents of the logs, but only indexes metadata about your logs as a set of labels for each log stream. A log stream is a set of logs which share the same labels. Labels help Loki to find a log stream within your data store, so having a quality set of labels is key to efficient query execution. Log data is then compressed and stored in chunks in an object store such as Amazon Simple Storage Service (S3) or Google Cloud Storage (GCS), or even, for development or proof of concept, on the filesystem. A small index and highly compressed chunks simplify the operation and significantly lower the cost of Loki. {{< figure src="../loki-overview-2.png" caption="Loki logging stack" >}} A typical Loki-based logging stack consists of 3 components: Agent - An agent or client, for example Promtail, which is distributed with Loki, or the Grafana Agent. The agent scrapes logs, turns the logs into streams by adding labels, and pushes the streams to Loki through an HTTP API. Loki - The main server, responsible for ingesting and storing logs and processing queries. It can be deployed in three different configurations, for more information see . for querying and displaying log data. You can also query logs from the command line, using or using the Loki API directly. Scalability - Loki is designed for scalability, and can scale from as small as running on a Raspberry Pi to ingesting petabytes a

In its most common deployment, simple scalable mode, Loki decouples requests into separate read and write paths, so that you can independently scale them, which leads to flexible large-scale installations that can quickly adapt to meet your workload at any given time. If needed, each of Loki's components can also be run as microservices designed to run natively within Kubernetes. Multi-tenancy - Loki allows multiple tenants to share a single Loki instance. With multi-tenancy, the data and requests of each tenant is completely isolated from the others. Multi-tenancy is by assigning a tenant ID in the agent. Third-party integrations - Several third-party agents (clients) have support for Loki, via plugins. This lets you keep your existing observability setup while also shipping logs to Loki. Efficient storage - Loki stores log data in highly compressed chunks. Similarly, the Loki index, because it indexes only the set of labels, is significantly smaller than other log aggregation tools. By leveraging object storage as the only data storage mechanism, Loki inherits the reliability and stability of the underlying object store. It also capitalizes on both the cost efficiency and operational simplicity of object storage over other storage mechanisms like locally attached solid state drives (SSD) and hard disk drives (HDD). The compressed chunks, smaller index, and use of low-cost object storage, make Loki less expensive to operate. LogQL, Loki's query language - is the query language for Loki. Users who are already familiar with the Prometheus query language, , will find LogQL familiar and flexible for generating queries against the logs. The language also facilitates the generation of metrics from log data, a powerful feature that goes well beyond log aggregation. Alerting - Loki includes a component called the , which can continually evaluate queries against your logs, and perform an action based on the result. This allows you to monitor your logs for anomalies or events. Loki integrates with , or the within Grafana. Grafana integration - Loki integrates with Grafana, Mimir, and Tempo, providing a complete observability stack, and seamless correlation between logs, metrics and traces.