This section describes the components installed by the Helm Chart.
Loki Read and Write
By default Loki will be installed in the scalable mode. This consists of a read and write component. These can be scaled-out independently.
This chart includes dashboards for monitoring Loki. These require the scrape configs defined in the
monitoring.selfMonitoring sections described below. The dashboards are deployed via a config map which can be mounted on a Grafana instance. The Dashboard require an installation of the Grafana Agent and the Prometheus operator. The agent is installed with this chart.
This chart installs the canary and its alerts by default. This is another tool to verify the Loki deployment is in a healthy state. It can be disabled with
By default and inspired by Grafana’s Tanka setup, the chart installs the gateway component which is an NGINX that exposes Loki’s API and automatically proxies requests to the correct Loki components (read or write, or single instance in the case of filesystem storage). The gateway must be enabled if an Ingress is required, since the Ingress exposes the gateway only. If the gateway is enabled, Grafana and log shipping agents, such as Promtail, should be configured to use the gateway. If NetworkPolicies are enabled, they are more restrictive if the gateway is enabled.
By default, this chart configures in-memory caching. If that caching does not work for your deployment, you should setup memcache.
Related Loki resources
Getting started with logging and Grafana Loki (Part 3 of 4)
Join this webinar to learn why correlating metrics and logs is critical across the development lifecycle, and how Loki helps reduce logging costs and operations overhead.
Logging with Loki: Essential configuration settings
This webinar focuses on Grafana Loki configuration including agents Promtail and Docker; the Loki server; and Loki storage for popular backends.