Loki

About

Unlike other logging systems, Loki is built around the idea of only indexing metadataabout 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 simplifiesthe operation and significantly lowers the cost of Loki. Read more

---

Relevant links

•   Homepage

---

Discuss this charm

Share your thoughts on this charm with the community on discourse.

Join the discussion

Loki Operator for K8s

Description

The Loki operator provides an open-source fully featured logging stack. This repository contains a Juju Charm for deploying Grafana Loki on Kubernetes clusters.

Usage

Create a Juju model for your operators, say "loki-k8s"

    juju add-model lma

The Loki Operator may be deployed using the Juju command line

    juju deploy loki-k8s

If required, you can remove the deployment completely:

    juju destroy-model -y loki-k8s --no-wait --force --destroy-storage

Note the --destroy-storage will delete any data stored by MySQL in its persistent store.

Relations

Currently supported relations are:

• Grafana aggregates logs obtained by Loki and provides a versatile dashboard to view these logs in configurable ways. Loki relates to Grafana over the grafana_datasource interface.
• Alertmanager receives alerts from Loki, aggregates and deduplicates them, then forwards them to specified targets. Loki relates to Alertmanager over the alertmanager_dispatch interface.
• In addition, this Loki charm allows relations with any charm that supports the loki_push_api relation interface.

OCI Images

This charm by default uses the latest stable version of the grafana/loki image.