apitech
/
loki
mirror of https://github.com/grafana/loki
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Like Prometheus, but for logs.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
4326 Commits
1078 Branches
354 Tags
750 MiB
 
 
 
 
 
 
Tag: Branch: Tree: 0f3eecd209
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '0f3eecd209'
${ noResults }
loki/docs/sources/release-notes/v2-7.md

2.5 KiB
Raw Blame History

title weight
V2.7 60

Version 2.7 release notes

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

Upgrade Considerations

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

Bug fixes

2.7.1

  • 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.