Skip to content
v2.5.0
2d9d0ee
Compare
Choose a tag to compare

🦖 🧡 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:
    • 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

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"
v2.4.2
525040a
Compare
Choose a tag to compare

Loki 2.4.2

Loki 2.4.2 is a patch fix release on 2.4.x

Defaults changes

2.4.2 makes the following changes to Loki defaults to improve usability, see 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 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)

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.4.2"
$ docker pull "grafana/promtail:2.4.2"

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.4.2/loki-linux-amd64.zip"
# extract the binary
$ unzip "loki-linux-amd64.zip"
# make sure it is executable
$ chmod a+x "loki-linux-amd64"
v2.4.1
f61a4d2
Compare
Choose a tag to compare

Loki 2.4.1

This is a patch fix release which fixes two important bugs found in the 2.4.0 release:

  • PR 4687 owen-d: Fixes a compactor panic when not using a tenant overrides file.
  • PR 4681 slim-bean: Fixes an incorrect initialization of the read target resulting in query gaps after a chunk is flushed and before the querier would download new index tables.

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.4.1"
$ docker pull "grafana/promtail:2.4.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.4.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.4.0
3987933
Compare
Choose a tag to compare

🎊 🌮 Loki 2.4.0 🌮 🎊

With Loki 2.4 we’ve focused on 2 main things:

  1. Making it easier than ever to get your logs into Loki.
  2. Making it easier to run and operate, anyone not using Kubernetes or allergic to 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 and in 2.4 the strict ordering constraint has been removed.
  • Scaling Loki is now much easier with a hybrid mode between a single binary and microservices we are calling the Simple Scalable Deployment. It’s now possible to scale 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 much simpler way.
  • We introduced a common config section and updated and updated a lot of defaults. This results in a 70% smaller Loki config and comes out of the box with more appropriate defaults and limits. Check out the example local config as the new reference for running Loki.
  • Recording rules are no longer marked experimental and have a much more resilient implementation which leverages the existing write ahead log code in Prometheus.
  • Do you use Kafka for your logs? You should check out the new Promtail Kafka Consumer which can easily get your logs out of Kafka and into Loki.
  • LogQL has received some nice enhancements thanks to the amazing Loki community in the form of group_left and group_right as well as the label_format and line_formatfunctions now support working with dates and times
  • Another great community contribution to Promtail allows it 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 please 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 config files.

Here is a list of limits changed:

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 -

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

Bug fixes

Lists of bug fixes for 2.4.x.

2.4.0 bug fixes

Here is a list of some of the more important fixes in 2.4.0:

  • 4598 kavirajk: Fix ip matcher lexer to differentiate filter from identifier
  • 4563 cyriltovena: Fixes the Series function to handle properly sharding.
  • 4518 slim-bean: Loki: Fix bug where items are returned to a sync.Pool incorrectly
  • 4411 slim-bean: Loki: Bug: frontend waiting on results which would never come
  • 4238 liguozhong: [fix] distributor: fix goroutine leak

Security fixes

List of security fixes for 2.4.x

2.4.0 security fixes

2.4.0 contains one fix which is security related

4627 Loki: 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. This PR restricts the type of HTTP methods allowed on each endpoint and disallows OPTIONS requests.

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.4.0"
$ docker pull "grafana/promtail:2.4.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.4.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.3.0
f5fd029
Compare
Choose a tag to compare

🥳🎉 Loki 2.3.0 🎉🥳

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 please 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, please check out 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.

For the full list of changes (almost 300!!) check out the CHANGELOG

Upgrade considerations

The path from 2.2.1 to 2.3.0 should be smooth, as always, please check out 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:

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.

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.3.0"
$ docker pull "grafana/promtail:2.3.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.3.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.2.1
babea82
Compare
Choose a tag to compare

2.2.1 fixes several important bugs, it is recommended everyone running 2.2.0 upgrade to 2.2.1

2.2.1 also adds the labelallow pipeline stage in Promtail which lets an allowlist be created for what labels will be sent by Promtail to Loki.

  • 3468 adityacs: Support labelallow stage in Promtail
  • 3502 cyriltovena: Fixes a bug where unpack would mutate log line.
  • 3540 cyriltovena: Support for single step metric query.
  • 3550 cyriltovena: Fixes a bug in MatrixStepper when sharding queries.
  • 3566 cyriltovena: Properly release the ticker in Loki client.
  • 3573 cyriltovena: Fixes a race when using specific tenant and multi-client.

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.2.1"
$ docker pull "grafana/promtail:2.2.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.2.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.2.0
a27c799
Compare
Choose a tag to compare

🎉🎉 Loki 2.2.0 is released!! 🎉🎉

Please read the Upgrade Guide before upgrading for a smooth experience.

Upgrade Guide TL;DR Loki 2.2 changes the internal chunk format which limits what versions you can downgrade to, a change was made in how many queries were allowed to be scheduled per tenant which might affect your max_query_parallelism and max_outstanding_per_tenant settings, and we fixed a mistake related scrape_configs which do not have a pipeline_stages defined. If you have any Promtail scrape_configs which do not specify pipeline_stages you should go read the upgrade notes!

With over 200 PR's 2.2 includes significant features, performance improvements, and bug fixes!

The most upvoted issue for Loki was closed in this release! Issue 74 requesting support for handling multi-line logs in Promtail was implemented in PR 3024. Thanks @jeschkies!

Other exciting news for Promtail, PR 3246 by @cyriltovena introduces support for reading Windows Events!

Switching to Loki, @owen-d has added a write ahead log to Loki! PR 2981 was the first of many as we have spent the last several months using and abusing our write ahead logs to flush out any bugs!

A significant number of the PR's in this release have gone to improving the features introduced in Loki 2.0. @cyriltovena overhauled the JSON parser in PR 3163 (and a few other PR's), to provide both a faster and smarter parsing to only extract JSON content which is used in the query output. The newest Loki squad member @dannykopping fine tuned the JSON parser options in PR 3280 allowing you to specific individual JSON elements, including support now for accessing elements in an array. Many, many other additional improvements have been made, as well as several fixes to the new LogQL features added some months ago, this upgrade should have everyone seeing improvements in their queries.

@cyriltovena also set his PPROF skills loose on the Loki write path which resulted in about 8x less memory usage on our distributors and a much more stable memory usage when ingesters are flushing a lot of chunks at the same time.

There are many other noteworthy additions and fixes, too many to list, but we should call out one more feature all you Google Cloud Platform users might be excited about: in PR 3083 @kavirajk added support to Promtail for listening on Google Pub/Sub topics, letting you setup log sinks for your GCP logs to be ingested by Promtail and sent to Loki!

For a full list of changes, please checkout the CHANGELOG

Thanks to everyone for another exciting Loki release!!

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.2.0"
$ docker pull "grafana/promtail:2.2.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.2.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.1.0
1b79df3
Compare
Choose a tag to compare

🎆🎁Happy Holidays from the Loki team!🎁🎆

Please enjoy Loki 2.1.0 to welcome in the New Year!

This release contains a number of fixes, performance improvements and enhancements to the 2.0.0 release!

Notable changes

Helm users read this!

The Helm charts have moved!

  • 2720 torstenwalter: Deprecate Charts as they have been moved

This was done to consolidate Grafana's helm charts for all Grafana projects in one place: https://github.com/grafana/helm-charts/

From now moving forward, please use the new Helm repo url: https://grafana.github.io/helm-charts

The charts in the Loki repo will soon be removed so please update your Helm repo to the new URL and submit your PR's over there as well

Special thanks to @torstenwalter, @unguiculus, and @scottrigby for their initiative and amazing work to make this happen!

Also go check out the microservices helm chart contributed by @unguiculus in the new repo!

Fluent bit plugin users read this!

Fluent bit officially supports Loki as an output plugin now! WoooHOOO!

However this created a naming conflict with our existing output plugin (the new native output uses the name loki) so we have renamed our plugin.

  • 2974 hedss: fluent-bit: Rename Fluent Bit plugin output name.

In time our plan is to deprecate and eliminate our output plugin in favor of the native Loki support. However until then you can continue using the plugin with the following change:

Old:

[Output]
    Name loki

New:

[Output]
    Name grafana-loki

Fixes

A lot of work went into 2.0 with a lot of new code and rewrites to existing, this introduced and uncovered some bugs which are fixed in 2.1:

  • 2807 cyriltovena: Fix error swallowed in the frontend.
  • 2805 cyriltovena: Improve pipeline stages ast errors.
  • 2824 owen-d: Fix/validate compactor config
  • 2830 sandeepsukhani: fix panic in ingester when not running with boltdb shipper while queriers does
  • 2850 owen-d: Only applies entry limits to non-SampleExprs.
  • 2855 sandeepsukhani: fix query intervals when running boltdb-shipper in single binary
  • 2895 shokada: Fix error 'Unexpected: ("$", "$") while parsing field definition'
  • 2902 cyriltovena: Fixes metric query issue with no grouping.
  • 2901 cyriltovena: Fixes a panic with the logql.NoopPipeline.
  • 2913 cyriltovena: Fixes logql.QueryType.
  • 2917 cyriltovena: Fixes race condition in tailer since logql v2.
  • 2960 sandeepsukhani: fix table deletion in table client for boltdb-shipper

Enhancements

A number of performance and resource improvements have been made as well!

  • 2911 sandeepsukhani: Boltdb shipper query readiness
  • 2875 cyriltovena: Labels computation LogQLv2
  • 2927 cyriltovena: Improve logql parser allocations.
  • 2926 cyriltovena: Cache label strings in ingester to improve memory usage.
  • 2931 cyriltovena: Only append tailed entries if needed.
  • 2973 cyriltovena: Avoid parsing labels when tailer is sending from a stream.
  • 2959 cyriltovena: Improve tailer matcher function.
  • 2876 jkellerer: LogQL: Add unwrap bytes() conversion function

Notable mentions

Thanks to @timbyr for adding an often requested feature, the ability to support environment variable expansion in config files!

  • 2837 timbyr: Configuration: Support environment expansion in configuration

Thanks to @huikang for adding a new docker-compose file for running Loki as microservices!

  • 2740 huikang: Deploy: add docker-compose cluster deployment file

All Changes

For a full list of changes, please checkout the CHANGELOG

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.1.0"
$ docker pull "grafana/promtail:2.1.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.1.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.0.1
d5141c0
Compare
Choose a tag to compare

2.0.1 is a special release, it only exists to add the v3 support to Loki's chunk format.

There is no reason to upgrade from 2.0.0 to 2.0.1

This chunk version is internal to Loki and not configurable, and in a future version v3 will become the default (Likely 2.2.0).

We are creating this to enable users to roll back from a future release which was writing v3 chunks, back as far as 2.0.0 and still be able to read chunks.

This is mostly a safety measure to help if someone upgrades from 2.0.0 and skips versions to a future version which is writing v3 chunks and they encounter an issue which they would like to roll back. They would be able to then roll back to 2.0.1 and still read v3 chunks.

It should be noted this does not help anyone upgrading from a version older than 2.0.0, that is you should at least upgrade to 2.0.0 before going to a newer version if you are on a version older than 2.0.0.

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.0.1"
$ docker pull "grafana/promtail:2.0.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.0.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.0.0
6978ee5
Compare
Choose a tag to compare

🎉🎉 Loki 2.0.0 is here!! 🎉🎉

We are extremely excited about the new features in 2.0.0, unlocking a whole new world of observability of our logs.

Thanks again for the many incredible contributions and improvements from the wonderful Loki community, we are very excited for the future!

Important Notes

Please Note There are several changes in this release which require your attention!

  • Anyone using a docker image please go read the upgrade guide!! There is one important consideration around a potentially breaking schema change depending on your configuration.
  • MAJOR changes have been made to the boltdb-shipper index, breaking changes are not expected but extra precautions are highly recommended, more details in the upgrade guide.
  • The long deprecated entry_parser config in Promtail has been removed, use pipeline_stages instead.

Check the upgrade guide for detailed information on all these changes.

2.0!!!!

There are too many PR's to list individually for the major improvements which we thought justified a 2.0 but here is the high level:

  • Significant enhancements to the LogQL query language!
    • Parse your logs to extract labels at query time.
    • Filter on query time extracted labels.
    • Format your log lines any way you please!
    • Graph the contents of your log lines as metrics, including support for many more of your favorite PromQL functions.
  • Generate prometheus alerts directly from your logs!
    • Create alerts using the same prometheus alert rule syntax and let Loki send alerts directly to your Prometheus Alertmanager!
  • boltdb-shipper is now production ready!
    • This is it! Now Loki only needs a single object store (S3,GCS,Filesystem...) to store all the data, no more Cassandra, DynamoDB or Bigtable!

We are extremely excited about these new features, expect some talks, webinars, and blogs where we explain all this new functionality in detail.

Notable mention

This is a small change but very helpful!

  • 2737 dlemel8: cmd/loki: add "verify-config" flag

Thank you @dlemel8 for this PR! Now you can start Loki with -verify-config to make sure your config is valid and Loki will exit with a status code 0 if it is!

All Changes

For a full list of changes, please checkout the CHANGELOG

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.0.0"
$ docker pull "grafana/promtail:2.0.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.0.0/loki-linux-amd64.zip"
# extract the binary
$ unzip "loki-linux-amd64.zip"
# make sure it is executable
$ chmod a+x "loki-linux-amd64"