Skip to content

chore(deps): update dependency grafana/loki to v2.6.1

Robert Stéphane requested to merge renovate/grafana-loki-2.x into main

This MR contains the following updates:

Package Update Change
grafana/loki minor v2.4.2 -> v2.6.1

Release Notes

grafana/loki

v2.6.1

Compare Source

Loki 2.6.1 is a patch fix release on 2.6.0

Notable changes:
  • MR 6658 JordanRushing: Updated the versions of dskit and memberlist to allow configuring cluster labels for memberlist. Cluster labels prevent mixing the members between two consistent hash rings of separate applications that are run on the same Kubernetes cluster.
  • MR 6681 MasslessParticle Fixed an HTTP connection leak between the querier and the compactor when the log entry deletion feature is enabled.
  • MR 6583 MasslessParticle Fixed noisy error messages when the log entry deletion feature is disabled for a tenant
Installation:

The components of Loki are currently distributed in plain binary form and as Docker container images. Choose what fits your use-case best.

Docker container:
$ docker pull "grafana/loki:2.6.1"
$ docker pull "grafana/promtail:2.6.1"
Binary

We provide pre-compiled binary executables for the most common operating systems and architectures. Choose from the assets below for the application and architecture matching your system. Example for Loki on the linux operating system and amd64 architecture:

$ curl -O -L "https://github.com/grafana/loki/releases/download/v2.6.1/loki-linux-amd64.zip"
### extract the binary
$ unzip "loki-linux-amd64.zip"
### make sure it is executable
$ chmod a+x "loki-linux-amd64"

v2.6.0

Compare Source

💪 Loki 2.6.0 💪

         🦵:leg:

Features and enhancements

  • Query multiple tenants at once. We've introduced cross-tenant query federation, which allows you to issue one query to multiple tenants and get a single, consolidated result. This is great for scenarios where you need a global view of logs within your multi-tenant cluster. For more information on how to enable this feature, see Multi-Tenancy.
  • Filter out and delete certain log lines from query results. This is particularly useful in cases where users may accidentally write sensitive information to Loki that they do not want exposed. Users craft a LogQL query that selects the specific lines they're interested in, and then can choose to either filter out those lines from query results, or permanently delete them from Loki's storage. For more information, see Logs Deletion.
  • Improved query performance on instant queries. Loki now splits instant queries with a large time range (for example, sum(rate({app="foo"}[6h]))) into several smaller sub-queries and executes them in parallel. Users don't need to take any action to enjoy this performance improvement; however, they can adjust the number of sub-queries generated by modifying the split_queries_by_interval configuration parameter, which currently defaults to 30m.
  • Support Baidu AI Cloud as a storage backend. Loki users can now use Baidu Object Storage (BOS) as their storage backend. See bos_storage_config for details.

For a full list of all changes please look at the CHANGELOG.

Upgrade Considerations

As always, please read the upgrade guide before upgrading Loki.

Bug fixes

2.6.0 bug fixes

V2.6.0 fixes numerous bugs.

A summary of some of the more important fixes:

  • MR 6152 Fixed a scenario where live tailing of logs could cause unbounded ingester memory growth.
  • MR 5685 Fixed a bug in Loki's push request parser that allowed users to send arbitrary non-string data as a log line. We now test that the pushed values are valid strings and return an error if values are not valid strings.
  • MR 5799 Fixed incorrect deduplication logic for cases where multiple log entries with the same timestamp exist.
  • MR 5888 Fixed a bug in the common configuration where the instance_interface_names setting was getting overwritten by the default ring configuration.
Installation:

The components of Loki are currently distributed in plain binary form and as Docker container images. Choose what fits your use-case best.

Docker container:
$ docker pull "grafana/loki:2.6.0"
$ docker pull "grafana/promtail:2.6.0"
Binary

We provide pre-compiled binary executables for the most common operating systems and architectures. Choose from the assets below for the application and architecture matching your system. Example for Loki on the linux operating system and amd64 architecture:

$ curl -O -L "https://github.com/grafana/loki/releases/download/v2.6.0/loki-linux-amd64.zip"
### extract the binary
$ unzip "loki-linux-amd64.zip"
### make sure it is executable
$ chmod a+x "loki-linux-amd64"

v2.5.0

Compare Source

🦖 🧡 Loki 2.5.0 🧡 🦖

It has been nearly 6 months since Loki 2.4 was released, and we’ve been busy making Loki better than ever. Here's a summary of new enhancements and important fixes.

Features and enhancements

For a full list of all changes please look at the CHANGELOG.

Upgrade Considerations

As always, please read the upgrade guide before upgrading Loki.

Changes to the config split_queries_by_interval

The most likely impact many people will see is Loki failing to start because of a change in the YAML configuration for split_queries_by_interval. It was previously possible to define this value in two places.

query_range:
  split_queries_by_interval: 10m

and/or

limits_config:
  split_queries_by_interval: 10m

In 2.5.0 it can only be defined in the limits_config section.

Loki will fail to start if you do not remove the split_queries_by_interval configuration parameter from the query_range section.

Additionally, it has a new default value of 30m rather than 0.

The CLI flag is not changed and remains querier.split-queries-by-interval.

More parallelism by default

We continue to move defaults in Loki to leverage parallelism in all configurations, including the single binary.

In v2.5, all queries will be split and sharded by default. This will likely result in increased memory and CPU usage for Loki processes during queries, if you didn’t previously have these values enabled.

Usage reporting

Loki 2.5 includes code we added to report anonymous usage statistics back to Grafana Labs, an issue was created to outline the intent, and what went into the final implementation can be seen here in the source.

Usage reporting helps provide anonymous information on how people use Loki and what the Loki team should focus on for features and documentation. No private information is collected, and all reports are completely anonymous.

If possible, we ask you to leave the usage reporting feature enabled and help us understand more about Loki! We are also working to figure out how we can share this info with the community so everyone can watch Loki grow.

If you would rather not participate in usage stats reporting, the feature can be disabled in config

analytics:
  reporting_enabled: false

Bug fixes

2.5.0 bug fixes

V2.5.0 fixes numerous bugs. The CHANGELOG has the complete list.

A summary of some of the more important fixes:

  • Query correctness:
    • MR 5474 cyriltovena: Disable sharding of count/avg when labels are mutated
    • MR 5444 cyriltovena: Do not insert missing point when sharding
    • MR 5423 cyriltovena: Correctly sets hash value for headblock iterator
    • MR 5289 cyriltovena: Fixes log deduplication when mutating Labels using LogQL
    • MR 5006 sandeepsukhani: Fix splitting of queries when step is larger than split interval
  • MR 5413 owen-d: A deadlock in the Azure blob client
  • MR 5334 kavirajk: A fix in live tailing that could lead to exploding memory usage
  • MR 5144 owen-d: A fix for the ruler when trying to use Basic Auth for remote write
  • Query cancellation:
    • MR 5113 kavirajk: Fix cancel issue between query-frontend and query scheduler
    • MR 5080 kavirajk: Handle context cancellation in some of the querier downstream requests
    • MR 5075 cyriltovena: Fixes a possible cancellation issue in the frontend
  • MR 4741 sandeepsukhani: An issue where retention didn't cleanup the index completely

Installation:

The components of Loki are currently distributed in plain binary form and as Docker container images. Choose what fits your use-case best.

Docker container:
$ docker pull "grafana/loki:2.5.0"
$ docker pull "grafana/promtail:2.5.0"
Binary

We provide pre-compiled binary executables for the most common operating systems and architectures. Choose from the assets below for the application and architecture matching your system. Example for Loki on the linux operating system and amd64 architecture:

$ curl -O -L "https://github.com/grafana/loki/releases/download/v2.5.0/loki-linux-amd64.zip"
### extract the binary
$ unzip "loki-linux-amd64.zip"
### make sure it is executable
$ chmod a+x "loki-linux-amd64"

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

  • If you want to rebase/retry this MR, click this checkbox.

This MR has been generated by Renovate Bot.

Edited by Robert Stéphane

Merge request reports