Release notes on Grafana Labs

Release cadence

Sat, 14 Mar 2026 10:06:05 +0000

Release cadence

Stable Releases

Loki releases (this includes Promtail, Loki Canary, etc.) use the following naming scheme: MAJOR.MINOR.PATCH.

MAJOR (roughly once a year): these releases include large new features and possible backwards-compatibility breaks.
MINOR (roughly once a quarter): these releases include new features which generally do not break backwards-compatibility, but from time to time we might introduce minor breaking changes, and we will specify these in our upgrade docs.
PATCH (roughly once or twice a month): these releases include bug and security fixes which do not break backwards-compatibility.

Note
While our naming scheme resembles Semantic Versioning, at this time we do not strictly follow its guidelines to the letter. Our goal is to provide regular releases that are as stable as possible, and we take backwards-compatibility seriously. As with any software, always read the release notes and the upgrade guide whenever choosing a new version of Loki to install.

New releases are based of a weekly release which we have vetted for stability over a number of weeks.

We strongly recommend keeping up-to-date with patch releases as they are released. We post updates of new releases in the #loki channel of our Slack community.

You can find all of our releases on GitHub and on Docker Hub.

Weekly Releases

Every Monday morning, we create a new “weekly” release from the tip of the main branch. These releases use the following naming scheme:

weekly-k<week-number>

<week-number>

These weekly releases are deployed across our Grafana Cloud Logs fleet of instances. We test these releases for stability by deploying them through development, pre-production, and production instances.

Generally these weekly releases are considered stable enough to run, but we provide zero stability guarantees and these releases should not be run in production unless you are willing to tolerate some risk.

You can find these releases on Docker Hub.

Which release will my merged PR be part of?

Once your PR is merged to main, you can expect it to become available in the next week’s weekly release. To find out which stable or weekly releases a commit is included in, use the following tool:

tools/which-release.sh

For example, this PR was merged into the commit named d434e80. Using the tool above, we can see that is part of release 2.8 and several weekly releases:

$ ./tools/which-release.sh d434e80                                 
Commit was found in the following releases:
  release-2.8.x
Commit was found in the following weekly builds:
  k136
  k137
  k138
  k139
  k140
  k141
  k142

v3.0

Sat, 14 Mar 2026 10:06:05 +0000

v3.0

Grafana Labs and the Loki team are excited to announce the release of Loki 3.0. Here’s a summary of new enhancements and important fixes.

For a full list of all changes and fixes, refer to the CHANGELOG.

Features and enhancements

Note
Note that Loki 3.0 defaults to using the v13 schema. All of the latest features are built against TSDB and the v13 Schema. This version of the schema is compatible with both Loki 2.9.x and Loki 3.0. The main change is to add support for Structured Metadata which is used by the new OTLP native endpoint and is enabled by default.

Key features in Loki 3.0.0 include the following:

Query acceleration with Bloom filters (experimental): This is designed to speed up filter queries, with best results for queries that are looking for a specific text string like an error message or UUID. For more information, refer to Query acceleration with Blooms.
Native OpenTelemetry Support: A simplified ingestion pipeline (Loki Exporter no longer needed) and a more intuitive query experience for OTel logs. For more information, refer to the OTel documentation.
Helm charts: A major upgrade to the Loki helm chart introduces support for Distributed mode (also known as microservices mode), includes memcached by default, and includes several updates to configurations to improve Loki operations.
Pattern match filter: LogQL now supports two new pattern match filter operators. You can match any word with just one control character and it is simpler and 10x faster than using regex.
Caching updates: This release includes multiple updates to caching to improve performance, add new configuration options and support for new features, deprecate features no longer needed, and add automatic background checks.
Lambda/Promtail: Support dropping labels (#10755) (ec54c72).
Profiling integration: Added profiling integrations to tracing instrumentation to allow getting a profile for a single request.
Docs improvements: All the Getting Started topics have been revised, including a new Quickstart to help new users get up and running with Loki faster. The Storage, Configuration Reference, and API documentation have been updated to reflect deprecated and removed code, configuration options, and API endpoints.

Deprecations

One of the focuses of Loki 3.0 was cleaning up unused code and old features that had been previously deprecated but not removed. Loki 3.0 removes a number of previous deprecations and introduces some new deprecations. Some of the main areas with changes include:

Deprecated storage options including the deprecation of the BoltDB store.
Deprecated configuration options.
API endpoint deprecations.

To learn more about breaking changes in this release, refer to the Upgrade guide.

Caution
Grafana Alloy is the new name for our distribution of the OTel collector. Grafana Agent has been deprecated and is in Long-Term Support (LTS) through October 31, 2025. Grafana Agent will reach an End-of-Life (EOL) on November 1, 2025. Read more about why we recommend migrating to Grafana Alloy.

Upgrade Considerations

The path from 2.9 to 3.0 includes several breaking changes. For important upgrade guidance, refer to the Upgrade Guide and the separate Helm Upgrade Guide.

Bug fixes

3.0.1 (2024-08-09)

deps: Bumped dependencies versions to resolve CVEs (#13833) (e13011d).
Fixed nil pointer dereference in bloomstore initialization (#12869) (167b468), closes #12270.

3.0.0 (2024-04-08)

All lifecycler configurations reference a valid IPv6 address and port combination (#11121) (6385b19).
deps: Update github.com/c2h5oh/datasize digest to 859f65c (main) (#10820) (c66ffd1).
deps: Update github.com/docker/go-plugins-helpers digest to 6eecb7b (main) (#10826) (fb9c496).
deps: Update github.com/grafana/gomemcache digest to 6947259 (main) (#10836) (2327789).
deps: Update github.com/grafana/loki/pkg/push digest to 583aa28 (main) (#10842) (02d9418).
deps: Update github.com/grafana/loki/pkg/push digest to cfc4f0e (main) (#10946) (d27c4d2).
deps: Update github.com/grafana/loki/pkg/push digest to e523809 (main) (#11107) (09cb9ae).
deps: Update github.com/joncrlsn/dque digest to c2ef48c (main) (#10947) (1fe4885).
deps: Update module google.golang.org/grpc [security] (main) (#11031) (0695424).
helm: Bump nginx-unprivilege to fix CVE (#10754) (dbf7dd4).
helm: Sidecar configuration for Backend (#10603) (c29ba97).
lambda-promtail Fix panic in lambda-promtail due to mishandling of empty DROP_LABELS env var. (#11074).
loki: Respect query matcher in ingester when getting label values (#10375) (85e2e52).
loki Generate tsdb_shipper storage_config even if using_boltdb_shipper is false (#11195).
loki Do not reflect label names in request metrics’ “route” label. (11551).
loki Fix duplicate logs from docker containers. (#11563).
loki Ruler: Fixed a panic that can be caused by concurrent read-write access of tenant configs when there are a large amount of rules. (#11601).
loki Fixed regression adding newlines to HTTP error response bodies which may break client integrations. (#11606).
loki Log results cache: compose empty response based on the request being served to avoid returning incorrect limit or direction. (#11657).
loki Fix semantics of label parsing logic of metrics and logs queries. Both only parse the first label if multiple extractions into the same label are requested. (#11587).
loki Background Cache: Fixes a bug that is causing the background queue size to be incremented twice for each enqueued item. (#11776).
loki: Parsing: String array elements were not being parsed correctly in JSON processing (#11921).
promtail: Correctly parse list of drop stage sources from YAML (#10848) (f51ee84).
promtail: Prevent panic due to duplicate metric registration after reloaded (#10798) (47e2c58).
promtail: Fix Promtail excludepath not evaluated on newly added files. (#9831).
tools/lambda-promtail: Do not evaluate empty string for drop_labels (#11074) (94169a0).

V2.9

Sat, 14 Mar 2026 10:06:05 +0000

V2.9

Grafana Labs is excited to announce the release of Loki 2.9.0 Here’s a summary of new enhancements and important fixes:

Features and enhancements

Structured metadata: The Structured Metadata feature, which was introduced as experimental in release 2.9.0, is generally available as of release 2.9.4.
Query Language Improvements: Several improvements to the query language that speed up line parsing and regex matching. PR #8646, PR #8659, PR #8724, PR #8734, PR #8739, PR #8763, PR #8890, PR #8914
Remote rule evaluation: Rule evaluation can now be handled by queriers to improve speed. PR #8744 PR #8848
Multi-store Index support: Loki now supports reading/writing indexes to multiple object stores which enables the use of different storage buckets across periods for storing index. PR #7754, PR #7447
New volume and volume_range endpoints: Two new endoints, index/volume and index/volume_range, have been added to Loki. They return aggregate volume information from the TSDB index for all streams matching a provided stream selector. This feature was introduced via multiple PRs, including PR #9988, PR #9966, PR #9833, PR #9832, PR #9776, PR #9762, PR #9704, PR #10248, PR #10099, PR #10076, PR #10047 and PR #10045
New Storage Client: Add support for IBM cloud object storage as storage client. PR #8826
Block queries by hash: Queries can now be blocked by a query hash. PR #8953
logfmt stage improvements: logfmt parser now performs non-strict parsing by default which helps scan semi-structured log lines. PR #9626
Deprecations
- Legacy index and chunk stores that are not “single store” (such as tsdb, boltdb-shipper) are deprecated. These storage backends are Cassandra (cassandra), DynamoDB (aws, aws-dynamo), BigTable (bigtable, bigtable-hashed), GCP (gcp, gcp-columnkey), and gRPC (grpc). See https://grafana.com/docs/loki/<LOKI_VERSION>/configure/storage.md for more information.
- The table-manager target is deprecated, because it is not used by “single store” implementations.
- The -boltdb.shipper.compactor.* CLI flags are deprecated in favor of -compactor.*.
- The -ingester.unordered-writes CLI flag is deprecated and will always default to true in the next major release.
- For the full list of deprecations, see CHANGELOG.md

Bug fixes

2.9.14 (2025-04-15)

deps: Upgrade golang.org/x/oauth2 to 0.27.0 (#16960) (fb70d03).
deps: Fix Loki CVEs for 2.9 (#17065) (5faccce).
deps: Remove remaining replaces to fix CVEs for 2.9.x (#17095) (26fcedb).
deps: Upgrade docker/docker used by 2.9.x (#17091) (914adec).
deps: Upgrade k8s.io/api used by Loki 2.9.x (#17093) (0da39f4).
deps: Upgrade packages used by docker/docker for 2.9.x (#17074) (2c8da3d).

2.9.13 (2025-03-12)

deps: Loki 2.9.x Bump Alpine and Go versions (#16294) (f2deeb7).

2.9.12 (2025-02-13)

deps: CVE updates for Loki 2.9.11 (#15647) (8447402).

2.9.11 (2024-12-04)

docker: Update Docker to 23.0.15 (#).
lamba-promtail: Lamba-promtail updates, some of which address CVEs(#14105).
promtail: Switch Promtail base image from Debian to Ubuntu to fix critical security issues (#15195).
storage: Fix bug in cache of the index object client(#10585).

2.9.10 (2024-08-09)

Update dependencies versions to remove CVE (#13835) (567bef2).

2.9.9 (2024 -07-04)

Ingester: Add ingester_chunks_flush_failures_total 12925.
Ingester: Add backoff to flush op 13140.

2.9.8 (2024-05-03)

deps: update module golang.org/x/net to v0.23.0 [security] (release-2.9.x) (#12865) (94e0029).

2.9.7 (2024-04-10)

Bump go to 1.21.9 and build image to 0.33.1 (#12542) (efc4d2f)

2.9.6 (2024-03-21)

Fixed Promtail failures connecting to local Loki installation (#12184) (8585e35).
Fixed an issue when using IPv6 where IPv6 addresses were not properly joined with ports. Use net.JoinHostPort to support IPv6 addresses. (#10650) (#11870) (7def3b4).
Updated google.golang.org/protobuf to v1.33.0 (#12269) (#12287) (3186520).

For a full list of all changes and fixes, refer to the CHANGELOG.

2.9.5 (2024-02-28)

Bumped base images and Go dependencies to address CVEs (#12092) (eee3598).

For a full list of all changes and fixes, refer to the CHANGELOG.

2.9.4 (2024-01-24)

Fixed a couple of data races that can cause panics due to concurrent read-write access of tenant configs.
Fixed a bug in the log results cache.
Fixed the cache to atomically check background cache size limit correctly.
Fixed the discrepancy between the semantics of logs and metrics queries.
Fixed promtail default scrape config causing CPU and memory load.
Updated golang.org/x/crypto to v0.18.0.

For a full list of all changes and fixes, refer to the CHANGELOG.

2.9.3 (2023-12-11)

Upgraded otelhttp from 0.40.0 -> 0.44.0 and base alpine image from 3.18.3 -> 3.18.5 to fix a few CVES (CVE-2023-45142, CVE-2022-21698, CVE-2023-5363).
Fixed querying ingester for label values with a matcher (previously didn’t respect the matcher).
Ensured all lifecycler cfgs ref a valid IPv6 addr and port combination.

For a full list of all changes and fixes, refer to the CHANGELOG.

2.9.2 (2023-10-16)

Upgraded go to v1.21.3, golang.org/x/net to v0.17.0 and grpc-go to v1.56.3 to patch CVE-2023-39325 / CVE-2023-44487

For a full list of all changes and fixes, refer to the CHANGELOG.

2.9.1 (2023-09-14)

Updated Docker base images to mitigate security vulnerability CVE-2022-48174
Fixed bugs in indexshipper (tsdb, boltdb-shipper) that could result in not showing all ingested logs in query results.

For a full list of all changes and fixes, refer to the CHANGELOG.

V2.8

Sat, 14 Mar 2026 10:06:05 +0000

V2.8

Grafana Labs is excited to announce the release of Loki 2.8. Here’s a summary of new enhancements and important fixes:

Features and enhancements

TSDB index no longer experimental After extensive testing of the new TSDB index in our Grafana Cloud Logs offering, we can safely announce that it is no longer experimental and encourage all Loki deployments to use it!
Query blocker Queries can now be blocked in the Querier/Ruler via a per-tenant runtime configuration.
New backend target A new, third target was added to Loki’s scalable configuration, which is the default configuration used in the Loki helm chart. This allows Loki to be run as 3 targets (read, write, and backend) and makes the read target stateless and therefore able to be run as a Kubernetes deployment that can be scaled automatically.

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

Upgrade Considerations

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

Bug fixes

2.8.6 (2023-10-17)

Upgrade go to v1.20.10, golang.org/x/net to v0.17.0 and grpc-go to v1.56.3 to patch CVE-2023-39325 / CVE-2023-44487

2.8.5 (2023-09-14)

Update Docker base images to mitigate security vulnerability CVE-2022-48174

2.8.2 (2023-05-03)

Update Go to 1.20.4 to address security vulnerabilities in the previous Go version.
Promtail: Add new decompression configuration to customize the decompressor behavior.

2.8.1 (2023-04-21)

Fix bug that was dropping index if period is a zero value.
Fix redis client to prevent it from incorrectly choosing cluster mode with local address.
Update go to 1.20.3 to address security vulnerabilities in the previous go version.
Update alpine image to 3.16.5 to address security vulnerabilities in the previous version.
Promtail: Fix journald support in amd64 binary build.

For a full list of all changes and fixes, look at the CHANGELOG.

V2.7

Sat, 14 Mar 2026 10:06:05 +0000

V2.7

Grafana Labs is excited to announce the release of Loki 2.7. Here’s a summary of new enhancements and important fixes:

Features and enhancements

New Internal Server and TLS TLS can now be configured everywhere and there is an internal server to allow ring, memberlist, and readiness handlers to continue to work without TLS.
Better Support for Azure Blob Storage thanks to the ability to use Azure’s Service Principal Credentials.
Logs can now be pushed from the Loki canary so you don’t have to rely on a scraping service to use the canary.
Additional label_format fields __timestamp__ and __line__.
fifocache has been renamed The in-memory fifocache has been renamed to embedded-cache. Check upgrade guide for more details
New HTTP endpoint for Ingester shutdown that will also delete the ring token.
Faster label queries thanks to new parallization.
Introducing Stream Sharding an experimental new feature to help deal with very large streams.
Promtail
- support for max stream limit
- config reload endpoint / signal
- compressed file support
- lambda-promtail now supports Kinesis data stream events
- matches for the journal reader
- basic tracing support

For a full list of all, look at the CHANGELOG.

Upgrade Considerations

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

Bug fixes

2.7.5 (2023-03-28)

Flush buffered logger on exit: this makes sure logs are printed if Loki crashes on startup.

2.7.4 (2023-02-24)

Fixed different streams for cri tags ending on the same stream.
Fixed the userdata field (from Windows Event Log) being scraped incorrectly.
Fixed vector() function producing wrong timestamp.
Fixed behavior for overlapping chunks with multiple stores.
Fixed logs results caching causing query-frontend to return logs outside of query window.
Fixed panics when:
- /scheduler/ring endpoint is requested with scheduler ring disabled.
- LogQL clones a specific query.
- Promtail deals with invalid calls to Details().

2.7.3 (2023-02-01)

Fixed a bug in compactor that caused divide-by-zero panics when startTime and endTime of a delete request were equal.
Fixed the output of the --version command that showed an incorrect version information.

2.7.2 (2023-01-25)

Fixed bug in validation of pattern and regexp parsers where missing or empty parameters for these parsers caused panics.
Fixed bugs in processing delete requests with line filters:
- Whole chunks covered by delete requests with a line filter were incorrectly skipped.
- Chunks partially covered by delete requests with a line filter were not properly processed. The part that was not covered by the delete request was rewritten with a line filter, while the part that was covered by the delete request was completely deleted.
Fixed bug in multi-tenant querying that caused HTTP 400 responses when multiple tenants where used in X-Scope-OrgID header like so tenant-a|tenant-b.
Upgraded Go build version and Docker container base images to 1.19.5 to mitigate GO-2022-1144 vulnerability.

2.7.1 (2022-12-09)

Add single compactor http client for delete and gennumber clients. This fixes a bug caused by the accidental introduction of different HTTP clients for compactor and gennumber operations that resulted in 404s when only the gennumber middlewares were enabled:

level=error ts=2022-10-18T14:13:41.598649348Z caller=delete_requests_client.go:211 msg="error getting delete requests from the store" err="unexpected status code: 404"
ts=2022-10-18T14:13:41.598697295Z caller=spanlogger.go:80 user=application level=error msg="failed loading deletes for user" err="unexpected status code: 404"

Change default deletion mode to filter-only on account of the bug (see below).

Known Issues

There is a bug with the experimental deletion mode in 2.6.x and 2.7.x that in some cases can cause the wrong chunks to be deleted. As a result we have changed the default deletion mode to filter-only until this bug has been addressed.

V2.6

Sat, 14 Mar 2026 10:06:05 +0000

V2.6

Grafana Labs is excited to announce the release of Loki 2.6. Here’s a summary of new enhancements and important fixes.

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, look at the CHANGELOG.

Upgrade Considerations

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

Bug fixes

2.6.1

v2.6.1 includes following fixes:

PR 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.
PR 6681 MasslessParticle Fixed an HTTP connection leak between the querier and the compactor when the log entry deletion feature is enabled.
PR 6583 MasslessParticle Fixed noisy error messages when the log entry deletion feature is disabled for a tenant

2.6.0 bug fixes

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

A summary of some of the more important fixes:

PR 6152 Fixed a scenario where live tailing of logs could cause unbounded ingester memory growth.
PR 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.
PR 5799 Fixed incorrect deduplication logic for cases where multiple log entries with the same timestamp exist.
PR 5888 Fixed a bug in the common configuration where the instance_interface_names setting was getting overwritten by the default ring configuration.

V2.5

Sat, 14 Mar 2026 10:06:05 +0000

V2.5

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

Thanks to @bboreham for taking a deep dive on the Go regexp library, and for creating a fork which greatly improves the performance of common regex uses cases in Loki.
Binary operations are now significantly faster, taking full advantage of Loki’s parallelism.
A new schema is available, which uses more path prefixes to avoid rate limits on S3.
That same schema change was also added to the filesystem store, which avoids using one directory to store every chunk.
A new capability for hedging requests to storage improves performance on highly parallelized queries. Refer to the hedging configuration under the storage_config block for more information.
Promtail has several new ways to ingest logs:
Promtail permits client-side global rate limiting and pipeline-configurable rate limiting.

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

V2.4

Sat, 14 Mar 2026 10:06:05 +0000

V2.4

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.

Features and enhancements

Loki no longer requires logs to be sent in perfect chronological order. 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 Simple scalable deployment scales Loki with new read and write targets. Where previously you would have needed Kubernetes and the microservices approach to start tapping into Loki’s potential, it’s now possible to do this in a simpler way.
The new common section 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 example local configuration as the new reference for running Loki.
Recording rules 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 Promtail Kafka Consumer 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 group_left and group_right. And, the label_format and line_format functions now support working with dates and times.
Another great community contribution allows Promtail to accept ndjson and plaintext log files over HTTP.

All in all, about 260 PR’s 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 CHANGELOG.

Upgrade Considerations

Please read the upgrade guide before updating Loki.

We made a lot of changes to Loki’s 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.

v2.4.0 changes to defaults

Here is a list of limit defaults that have changed in v2.4.0:

config	new default	old default
ingestion_rate_strategy	“global”	“local”
max_global_streams_per_user	5000	0 (no limit)
max_query_length	“721h”	“0h” (no limit)
max_query_parallelism	32	14
max_streams_per_user	0 (no limit)	10000
reject_old_samples	true	false
reject_old_samples_max_age	“168h”	“336h”
per_stream_rate_limit	3MB	-
per_stream_rate_limit_burst	15MB	-

We have enabled the in-memory FIFO cache by default when no existing external cache is configured. This helps improve Loki’s performance, however it will also allow Loki to consume more memory.

v2.4.2 changes to defaults

Here is a list of limit defaults that have changed in v2.4.2, add in PR 5077:

config	new default	old default
parallelise_shardable_queries	true	false
split_queries_by_interval	30m	0s
query_ingesters_within	3h	0s
max_chunk_age	2h	1h
max_concurrent	10	20

Bug fixes

2.4.2 bug fixes

2.4.2 fixes these bugs:

PR 4968 trevorwhitney: Fixes a bug in which querying ingesters wrongly returns a ruler, causing the internal server error code = Unimplemented.
PR 4875 trevorwhitney: Honor the replication factor specified in the common configuration block when memberlist is the consistent hash ring store.
PR 4792 AndreZiviani: Corrects the default values of configuration options in the documentation for:
- scheduler_dns_lookup_period
- min_ready_duration
- final_sleep
- max_transfer_retries
- chunk_retain_period
- chunk_target_size
- batch_size
- timeout (for Redis requests)

2.4.1 bug fixes

2.4.1 fixes two bugs in the 2.4.0 release:

PR 4687 owen-d: Eliminate a compactor panic when not using a tenant overrides file.
PR 4681 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.

2.4.0 bug fixes

Here are some of the more important fixes in version 2.4.0:

PR 4598 kavirajk: Fix the IP matcher lexer to differentiate a filter from an identifier.
PR 4563 cyriltovena: Fixes the Series function to properly handle sharding.
PR 4518 slim-bean: Fixes a bug in which items are returned to a sync.Pool incorrectly.
PR 4411 slim-bean: Fixes a frontend bug which caused it to wait for results which would never arrive.
PR 4238 liguozhong: Fixes a distributor goroutine leak.

Security fixes

2.4.0 security fixes

Version 2.4.0 contains one security-related fix:

PR 4627 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.

V2.3

Sat, 14 Mar 2026 10:06:05 +0000

V2.3

The Loki team is excited to announce the release of Loki 2.3!

It’s been nearly 6 months since 2.2 was released and we have made good use of that time to bring forward several significant improvements and requested features.

2.3 is also the first version of Loki released under the AGPLv3 license. You can read more about our licensing here.

Some parts of the Loki repo will remain Apache-2.0 licensed (mainly clients and some tooling), for more details read LICENSING.md.

Features and enhancements

Loki now has the ability to apply custom retention based on stream selectors! This will allow much finer control over log retention all of which is now handled by Loki, no longer requiring the use of object store configs for retention.
Coming along hand in hand with storing logs for longer durations is the ability to delete log streams. The initial implementation lets you submit delete request jobs which will be processed after 24 hours.
A very exciting new LogQL parser has been introduced: the pattern parser. Much simpler and faster than regexp for log lines that have a little bit of structure to them such as the Common Log Format. This is now Loki’s fastest parser so try it out on any of your log lines!
Extending on the work of Alerting Rules, Loki now accepts recording rules. This lets you turn your logs into metrics and push them to Prometheus or any Prometheus compatible remote_write endpoint.
LogQL can understand IP addresses! This enables filtering on IP addresses and subnet ranges.

For those of you running Loki as microservices, the following features will improve performance operations significantly for many operations.

We created an index gateway which takes on the task of downloading the boltdb-shipper index files allowing you to run your queriers without any local disk requirements, this is really helpful in Kubernetes environments where you can return your queriers from Statefulsets back to Deployments and save a lot of PVC costs and operational headaches.
Ingester queriers are now shardable, this is a significant performance boost for high volume log streams when querying recent data.
Instant queries can now be split and sharded making them just as fast as range queries.

A very common feature requested has also been included in 2.3:

3919 github-vincent-miszczak: Add ingester.autoforget-unhealthy-timeout opt-in feature

Without revisiting the decisions and discussions around the somewhat controversial behavior of unhealthy ingesters, you can now decided how you would like them to be handled: manually or automatically.

Lastly several useful additions to the LogQL query language have been included:

More text/template functions are included for label_format and line_format with PR 3515, for more information,see the documentation for template functions.
Also support for math functions withing label_format and line_format was included with 3434.
Two additional metric functions with some interesting use cases first_over_time and last_over_time were added in PR 3050. These can be useful for some down sampling approaches where instead of taking an average, max, or min of samples over a range in a metrics query, you can select the first or last log line to use from that range.

Upgrade considerations

The path from 2.2.1 to 2.3.0 should be smooth, as always, read the Upgrade Guide for important upgrade guidance.

One change we consider noteworthy however is:

3216 sandeepsukhani: check for stream selectors to have at least one equality matcher.

This change now rejects any query which does not contain at least one equality matcher, an example may better illustrate:

{namespace=~".*"}

This query will now be rejected, however there are several ways to modify it for it to succeed:

Add at least one equals label matcher:

{cluster="us-east-1",namespace=~".*"}

Use .+ instead of .*

{namespace=~".+"}

This difference may seem subtle but if we break it down . matches any character, * matches zero or more of the preceding character and + matches one or more of the preceding character. The .* case will match empty values where .+ will not, this is the important difference. {namespace=""} is an invalid request (unless you add another equals label matcher like the example above).

The reasoning for this change has to do with how index lookups work in Loki, if you don’t have at least one equality matcher Loki has to perform a complete index table scan which is an expensive and slow operation.

Security fixes

List of security fixes for 2.3.x.

2.3.0 security fixes

2.3.0 contains an important security fix:

4020 simonswine: Restrict path segments in TenantIDs (CVE-2021-36156 CVE-2021-36157).

Note
Exploitation of this vulnerability requires the ability for an attacker to craft and send directly to Loki an X-Scope-OrgID header, end users should not have the ability to create and send this header directly to Loki as it controls access to tenants and is important to control setting of this header for proper tenant isolation and security. We always recommend having a proxy or gateway be responsible for setting the X-Scope-OrgID.

Bug fixes

Lists of bug fixes for 2.3.x.

2.3.0 bug fixes

An important fix for leaking resources was patched with 3733, when queries were canceled a goroutine was left running which would hold memory resources creating a memory leak.
3686 fixes a panic with the frontend when use with downstream URL. Note we recommend using the GRPC Pull Model, better performance and fair scheduling between tenants can be obtained with the GPRC Pull Model.

Release notes on Grafana Labs

Release cadence

Release cadence

Stable Releases

Weekly Releases

Which release will my merged PR be part of?

v3.0

v3.0

Features and enhancements

Deprecations

Upgrade Considerations

Bug fixes

3.0.1 (2024-08-09)

3.0.0 (2024-04-08)

V2.9

V2.9

Features and enhancements

Bug fixes

2.9.14 (2025-04-15)

2.9.13 (2025-03-12)

2.9.12 (2025-02-13)

2.9.11 (2024-12-04)

2.9.10 (2024-08-09)

2.9.9 (2024 -07-04)

2.9.8 (2024-05-03)

2.9.7 (2024-04-10)

2.9.6 (2024-03-21)

2.9.5 (2024-02-28)

2.9.4 (2024-01-24)

2.9.3 (2023-12-11)

2.9.2 (2023-10-16)

2.9.1 (2023-09-14)

V2.8

V2.8

Features and enhancements

Upgrade Considerations

Bug fixes

2.8.6 (2023-10-17)

2.8.5 (2023-09-14)

2.8.2 (2023-05-03)

2.8.1 (2023-04-21)

V2.7

V2.7

Features and enhancements

Upgrade Considerations

Bug fixes

2.7.5 (2023-03-28)

2.7.4 (2023-02-24)

2.7.3 (2023-02-01)

2.7.2 (2023-01-25)

2.7.1 (2022-12-09)

Known Issues

V2.6

V2.6

Features and enhancements

Upgrade Considerations

Bug fixes

2.6.1

2.6.0 bug fixes

V2.5

V2.5

Features and enhancements

Upgrade Considerations

Changes to the config split_queries_by_interval

More parallelism by default

Usage reporting

Bug fixes

2.5.0 bug fixes

V2.4

V2.4

Features and enhancements

Upgrade Considerations

v2.4.0 changes to defaults

v2.4.2 changes to defaults

Bug fixes

2.4.2 bug fixes

2.4.1 bug fixes

2.4.0 bug fixes

Security fixes

2.4.0 security fixes

Changes to the config `split_queries_by_interval`