Loki
Horizontally scalable log aggregation system inspired by Prometheus.
Open the official app on grafana.com
This tool is hosted by its maintainers. Click below to open grafana.com in a new tab — it's their official demo.
Browse developer tools →What's next with Loki?
Choose how you want to get started.
Use it free
Open the official tool or demo — no account needed.
Self-host it
Run the open-source version on your own infrastructure.
What is Loki?
Loki is an open-source log aggregation system designed to store and query logs from applications and infrastructure at scale. It addresses the challenge of managing large volumes of unstructured log data by using a label-based indexing approach instead of full-text indexing, which reduces storage costs and operational complexity. Developed by Grafana Labs and released under the AGPL-3.0 license, Loki is used by DevOps teams, cloud providers, and enterprises to centralize log management while maintaining flexibility and cost-efficiency. Its horizontal scalability and multi-tenancy make it suitable for environments with diverse log sources, from microservices to Kubernetes clusters. By abstracting log content from indexing, Loki enables efficient querying and analysis without compromising performance or durability, making it a key component in observability stacks.
How it works
Loki is a horizontally scalable, multi-tenant log aggregation system inspired by Prometheus. Unlike traditional log systems that index full log content, Loki indexes only labels associated with each log stream, enabling cost-effective storage and efficient querying. Its primary purpose is to provide a centralized solution for collecting, storing, and querying logs from distributed systems. It is designed to integrate with existing observability tools and support real-time monitoring without requiring significant infrastructure changes. Loki supports persistent storage via object storage (e.g., S3, Azure Blob Storage) for petabyte-scale log retention. It allows logs to be ingested in any format, with optional labeling for filtering and analysis. Integration with Grafana enables visualization and alerting based on log patterns.
How to use it
- 1Deploy Loki using a containerized setup or cloud provider services. 2. Configure a log shipper (e.g., Promtail) to collect logs from sources like containers, servers, or applications. 3. Define labels for each log stream to enable filtering during queries. 4. Use Grafana or Loki’s query language (Loki DSL) to search and visualize logs based on labels and timestamps. Practical tips: Store logs in object storage for long-term retention, set retention policies to manage costs, and leverage Grafana’s dashboards for real-time monitoring. Ensure log shippers are configured to handle high-throughput scenarios.
What it can do
- log aggregation
Use cases
Assumptions and limitations
Assumptions
- source: https://github.com/grafana/loki
- license: AGPL-3.0 — free to use
- privacy: Self-hosted — you control your data
Limitations
- Limited full-text search capabilities compared to systems like Elasticsearch
- Dependence on external object storage for persistent storage
- Complex setup required for advanced label-based filtering
- Lack of built-in real-time analytics pipelines
- Performance degradation with unstructured or unlabeled log streams
Understanding the result
Horizontally scalable log aggregation system inspired by Prometheus.
Tool details
- Clearly flagged when a network request is needed.
- No account, no sign-up, and no tracking of your content.
- Powered by (MIT).
- Built with
- (grafana/loki)
- License
- MIT
- Runs locally
- No — requires a network request
- Verification
- Not yet verified
- Input
- Query
- Output
- Text
Built with grafana/loki. OpenToolVault provides the discovery and browser interface while crediting the original project maintainers.
- Built with
- License
- MIT
Open-source project
OpenToolVault is an independent directory. We are not affiliated with or endorsed by this project.
References
- / — GitHub Repository
Upstream project · GitHub
- AGPL-3.0 License
Upstream project
Frequently asked
What is Loki and how does it differ from traditional log systems?
Loki is a log aggregation system that indexes log streams by labels rather than full content, reducing storage costs and complexity. Unlike systems like Elasticsearch, it avoids full-text indexing, making it more scalable for large-scale environments. It integrates with Grafana for visualization and is optimized for observability workflows.
How does Loki handle log storage and retrieval?
Loki stores logs in object storage (e.g., S3, Azure Blob Storage) for durability and scalability. Logs are grouped into streams with labels for metadata. Retrieval is performed via label-based queries, which filter streams without scanning entire log content. This design minimizes computational overhead and enables cost-effective long-term retention.
How do I set up Loki with Promtail for Kubernetes logs?
Deploy Loki as a Kubernetes Deployment, then configure Promtail as a DaemonSet to collect logs from pods. Define labels in Promtail’s config file to categorize logs (e.g., app=web, env=production). Use Loki’s query interface or Grafana to filter logs by labels and timestamps. Ensure object storage is configured for persistent storage.
How does Loki compare to Elasticsearch or Fluent Bit?
Loki differs from Elasticsearch by avoiding full-text indexing, which reduces resource usage but limits advanced search capabilities. Compared to Fluent Bit, Loki focuses on log storage and querying rather than real-time processing. It integrates with Grafana for visualization, whereas Elasticsearch requires separate tools for analytics.
How do I troubleshoot missing logs in Loki?
Check if logs are being ingested by verifying Promtail’s status and logs. Ensure labels are correctly configured to match query filters. Validate object storage permissions for persistent storage. Use Loki’s debug endpoints to inspect incoming streams. If logs are missing, review retention policies and storage backend configurations.