Logging Architecture

NOTE: Loki is deprecated and is planned to be removed. If you want to install a custom Loki stack, take a look at this tutorial.

Architecture diagram

Process flow

  1. Container logs are stored under the var/log directory and its subdirectories.
  2. The agent detects any new log files in the folder and tails them.
  3. The agent queries the Kubernetes API Server for additional Pod metadata, such as Pod annotations and labels.
  4. The agent enriches log data with labels and sends them to the Loki server.
  5. The Loki server processes the log data and stores it in the log store. The data is indexed based on the passed labels
  6. The user queries the logs using Grafana dashboards to analyze and visualize logs fetched and processed by Loki. Learn more about accessing Grafana.

With the integration of Kyma's telemetry component, you can use additional functionality:

  1. The telemetry operator provides your custom output configuration for Fluent Bit.
  2. As specified in your configuration, Fluent Bit sends the log data to observability systems outside the Kyma cluster.
  3. The user accesses the external observability system to analyze and vizualize the logs.