Project: Grafana Loki (Observability and Analysis / Observability)
File: v2-5.md

title: V2.5 description: Version 2.5 release notes weight: 77 It has been nearly 6 months since Loki 2.4 was released, and weve been busy making Loki better than ever. Here's a summary of new enhancements and important fixes. Thanks to @bboreham for taking a deep dive on the Go `regexp` library, and for creating a fork which greatly , taking full advantage of Loki's parallelism. , which uses more path prefixes to avoid rate limits on S3. That same schema change , which avoids using one directory to store every chunk. A new capability for improves performance on highly parallelized queries. Refer to the under the `storage_config` block for more information. Promtail has several new ways to ingest logs: The . . . Promtail permits and . For a full list of all changes, look at the . As always, please read the before upgrading Loki. The most likely impact many people will see is Loki failing to start because of a change in the YAML configuration for `splitqueriesby_interval`. It was previously possible to define this value in two places. ```yaml query_range: splitqueriesby_interval: 10m ``` and/or ```yaml limits_config: splitqueriesby_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`. 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 didnt previously have these values enabled. Loki 2.5 includes code we added to report anonymous usage statistics back to Grafana Labs, , and what went into the final implementation . 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, ``` analytics: reporting_enabled: false ``` V2.5.0 fixes numerous bugs. The has the complete list. A summary of some of the more important fixes: Query correctness: cyriltovena*: Disable sharding of count/avg when labels are mutated cyriltovena*: Do not insert missing point when sharding cyriltovena*: Correctly sets hash value for headblock iterator cyriltovena*: Fixes log deduplication when mutating Labels using LogQL sandeepsukhani*: Fix splitting of queries when step is larger than split interval owen-d*: A deadlock in the Azure blob client kavirajk*: A fix in live tailing that could lead to exploding memory usage owen-d*: A fix for the ruler when trying to use Basic Auth for remote write Query cancellation: kavirajk*: Fix cancel issue between query-frontend and query scheduler kavirajk*: Handle `context` cancellation in some of the `querier` downstream requests cyriltovena*: Fixes a possible cancellation issue in the frontend sandeepsukhani*: An issue where retention didn't cleanup the index completely