chore(deps): update container image grafana/promtail to v2.2.1 - autoclosed #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.6.0->2.2.1Release Notes
grafana/loki
v2.2.1Compare Source
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
labelallowpipeline stage in Promtail which lets an allowlist be created for what labels will be sent by Promtail to Loki.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:
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
Lokion thelinuxoperating system andamd64architecture:v2.2.0Compare Source
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!
Thanks to everyone for another exciting Loki release!!
Please read the Upgrade Guide before upgrading for a smooth experience.
TL;DR Loki 2.2 changes the internal chunk format which limits what versions you can downgrade to, a bug in how many queries were allowed to be scheduled per tenant was fixed which might affect your
max_query_parallelismandmax_outstanding_per_tenantsettings, and we fixed a mistake relatedscrape_configswhich do not have apipeline_stagesdefined. If you have any Promtailscrape_configswhich do not specifypipeline_stagesyou should go read the upgrade notes!All Changes
Loki
_entryexist.0976147Promtail
client.StopproperlyLogcli
Jsonnet
fluentd
fluent bit
Docker Logging Driver
Docs
config.expand-envflag in the doc.multilinedocumentation.Build
Tooling
Notes
This release was created from revision
8012362(Which was PR 3460)Dependencies
7dac811v2.1.0Compare Source
Happy Holidays from the Loki team! Please enjoy a new Loki release to welcome in the New Year!
2.1.0 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!
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.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:
New:
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:
Enhancements
A number of performance and resource improvements have been made as well!
Notable mentions
Thanks to @timbyr for adding an often requested feature, the ability to support environment variable expansion in config files!
Thanks to @huikang for adding a new docker-compose file for running Loki as microservices!
All Changes
Loki
Helm
helm initJsonnet
Docs
Promtail
Logcli
Build
Fluentd
Notes
This release was created from revision
ae9c4b8(Which was PR 2960) and the following PR's were cherry-pickedDependencies
85942c5v2.0.1Compare Source
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.
v2.0.0Compare Source
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!
entry_parserconfig 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:
** 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.
** Create alerts using the same prometheus alert rule syntax and let Loki send alerts directly to your Prometheus Alertmanager!
** 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!
Thank you @dlemel8 for this PR! Now you can start Loki with
-verify-configto make sure your config is valid and Loki will exit with a status code 0 if it is!All Changes
Loki
entry_parserfrom scrapeconfigDocs
Helm
FluentD
Fluent Bit
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.