Like Prometheus, but for logs!
Grafana Loki is a set of components that can be composed into a fully featured logging stack.
Unlike other logging systems, Loki is built around the idea of only indexing metadata about your logs: labels (just like Prometheus labels). Log data itself is then compressed and stored in chunks in object stores such as S3 or GCS, or even locally on the filesystem. A small index and highly compressed chunks simplifies the operation and significantly lowers the cost of Loki.
- Overview
- Installation
- Getting Started
- Best Practices
- Configuration
- Clients
- LogQL
- Operations
- HTTP API
- Architecture
- Community
- Loki Maintainers Guide
When you contribute to documentation, it is a good practice to build the docs on your local machine to make sure your changes appear as you expect. This README explains the process for doing that.
Docker >= 2.1.0.3
- In the command line, make sure you are in the docs folder:
cd docs
. - Run
make docs
. This launches a preview of the docs website athttp://localhost:3002/docs/loki/latest/
which will refresh automatically when changes to content in thesources
directory are made.
Edit content in the sources
directory.
The side menu is built automatically from the folder structure. Ordering is done with the weight
front matter param.
Images are sourced in this repo alonside content. They will sync to the website repo just like markdown files.
When a PR is merged to master with changes in the docs/sources
directory, those changes are automatically synched to the grafana/website repo and published to the staging site.
Generally, someone from marketing will publish to production each day, so as long as the sync is successful your docs edits will be published.