Grafana Labs introduced Tempo, a new tool for tracking dependencies, and released the new major version 2.0 of its logging tool Loki. With Grafana Tempo, the provider of monitoring, logging and tracing software relies on a distributed, scalable tracing system that brings together metric data, logs and traces. Tempo should work together with existing tools of the Grafana suite, but also be compatible with open source tracing tools such as Jaeger, OpenTelemetry and others.

Loki 2.0 generates warnings directly from the logs According to the provider, Loki 2.0 brings improvements to the LogQL Query Language with the most important innovations: Logs can now apparently be parsed to create labels to create at query time. Extracted labels can be filtered by users during the query, the formatting of log lines should now be customized and users can use the contents of log lines directly for functions of PromQL (Prometheus Query Language). Metric data should now be able to be graphically visualized in a more diverse way than before. Another new feature is that Prometheus warnings can be generated directly from the logs, and the boltdb-shipper is ready for production with the new release .

This means that Loki will no longer have to rely on databases like Cassandra, DynamoDB or Bigtable to store data, but rather with an object store like S3, GCS or the file system. A small change is of practical importance: If users start Loki with the command – verify-config , they can immediately check whether their own configuration is valid or not. Loki will respond with the status code 0 if the configuration fits.

Tangible changes and an upgrade guide According to the release notes, the new major release from Loki confronts developers with some tangible changes. Grafana particularly recommends developers who use a Docker image (including helmet, Tanka, docker-compose and the like) to consult the upgrade guide intended for this before the upgrade: Depending on the previous configuration, breaking changes must obviously be observed, the guide is intended to provide guidance on how to circumvent related problems. Significant changes concern the boltdb-shipper index , and the configuration

which was marked as deprecated a long time ago.