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

title: V2.4 description: Version 2.4 release notes weight: 88 Loki 2.4 focuses on two items: Making it easier to get your logs into Loki. Making Loki easier to run and operate. Anyone not using Kubernetes or avoiding microservices should pay close attention: this release has a lot for you. Support for out of order logs is one of the most highly requested features for Loki. The strict ordering constraint has been removed. Scaling Loki is now easier with a hybrid deployment mode that falls between our single binary and our microservices. The scales Loki with new `read` and `write` targets. Where previously you would have needed Kubernetes and the microservices approach to start tapping into Lokis potential, its now possible to do this in a simpler way. The new results in a 70% smaller Loki configuration. Pair that with updated defaults and Loki comes out of the box with more appropriate defaults and limits. Check out the as the new reference for running Loki. are no longer an experimental feature. We've given them a more resilient implementation which leverages the existing write ahead log code in Prometheus. The new can easily get your logs out of Kafka and into Loki. There are nice LogQL enhancements*, thanks to the amazing Loki community. LogQL now has . And, the `labelformat` and `lineformat` functions now support . Another great community contribution allows Promtail to . All in all, about 260 PRs went into Loki 2.4, and we thank everyone for helping us make the best Loki yet. For a full list of all changes, look at the . Please read the before updating Loki. We made a lot of changes to Lokis configuration as part of this release. We have tried our best to make sure changes are compatible with existing configurations, however some changes to default limits may impact users who didn't have values explicitly set for these limits in their configuration files. Here is a list of limit defaults that have changed in

| config | new default | old default | | | | | | ingestionratestrategy | "global" | "local" | | maxglobalstreamsperuser | 5000 | 0 (no limit) | | maxquerylength | "721h" | "0h" (no limit) | | maxqueryparallelism | 32 | 14 | | maxstreamsper_user | 0 (no limit) | 10000 | | rejectoldsamples | true | false | | rejectoldsamplesmaxage | "168h" | "336h" | | perstreamrate_limit | 3MB | - | | perstreamratelimitburst | 15MB | - | We have enabled the when no existing external cache is configured. This helps improve Loki's performance, however it will also allow Loki to consume more memory. Here is a list of limit defaults that have changed in v2.4.2, add in : | config | new default | old default | | | | | | paralleliseshardablequeries | true | false | | splitqueriesby_interval | 30m | 0s | | queryingesterswithin | 3h | 0s | | maxchunkage | 2h | 1h | | max_concurrent | 10 | 20 | 2.4.2 fixes these bugs: trevorwhitney: Fixes a bug in which querying ingesters wrongly returns a ruler, causing the internal server error `code = Unimplemented`. trevorwhitney: Honor the replication factor specified in the common configuration block when `memberlist` is the consistent hash ring store. AndreZiviani: Corrects the default values of configuration options in the documentation for: `schedulerdnslookup_period` `minreadyduration` `final_sleep` `maxtransferretries` `chunkretainperiod` `chunktargetsize` `batch_size` `timeout` (for Redis requests) 2.4.1 fixes two bugs in the 2.4.0 release: owen-d*: Eliminate a compactor panic when not using a tenant overrides file. slim-bean*: Correct the initialization of the `read` target. Incorrect initialization resulted in query gaps after a chunk was flushed and before the querier downloaded new index tables. Here are some of the more important fixes in version 2.4.0: kavirajk*: Fix the IP matcher lexer to differentiate a filter from an identifier. cyriltovena*: Fixes the Series function to properly handle sharding. slim-bean*: Fixes a bug in which items are returned to a sync.Pool incorrectly. slim-bean*: Fixes a frontend bug which caused it to wait for results which would never arrive. liguozhong*: Fixes a distributor goroutine leak. Version 2.4.0 contains one security-related fix: Explicitly define allowed HTTP methods on HTTP endpoints. A community user noticed that all Loki endpoints would respond to HTTP OPTIONS requests, and the proxy they placed in front of Loki responsible for HTTP authentication would pass OPTIONS requests unauthenticated to Loki, allowing users to make unauthenticated/unauthorized queries to Loki. The fix restricts the type of HTTP methods allowed on each endpoint and disallows OPTIONS requests.