This repository was archived by the owner on Apr 21, 2026. It is now read-only.
v1.16-4.10/outputs Update all dependencies#222
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
Conversation
2336379 to
93e89a4
Compare
fbe3306 to
02b5527
Compare
02b5527 to
cb9760b
Compare
cb9760b to
b50d933
Compare
a171262 to
44f5e6c
Compare
609ee0d to
5c242c4
Compare
c85056c to
c182ead
Compare
eb85d3f to
d5206c3
Compare
91c48ab to
d0fdba7
Compare
d0fdba7 to
f8c3ac0
Compare
f8c3ac0 to
fa1ee44
Compare
fa1ee44 to
ff1991d
Compare
ff1991d to
5c2cbb1
Compare
5bee6a6 to
261f9c1
Compare
261f9c1 to
d6292dc
Compare
1db44ca to
de59d71
Compare
a146d6b to
d295af6
Compare
d295af6 to
6eca5bd
Compare
6eca5bd to
b4bbd5a
Compare
63779e6 to
8b4a7ce
Compare
8b4a7ce to
9fb7faa
Compare
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
'0.14.4'→'0.15.0''1.2.20'→'1.3.0''0.19.4'→'0.19.6''3.5.0'→'3.7.0''0.21.0'→'0.26.0'Release Notes
DataDog/fluent-plugin-datadog (fluent-plugin-datadog)
v0.15.0Compare Source
grafana/loki (fluent-plugin-grafana-loki)
v1.3.0What's New??
With 1.3.0 we are excited to announce several improvements focusing on performance!
First and most significant is the Query Frontend:
The query frontend allows for sharding queries by time and dispatching them in parallel to multiple queriers, giving true horizontal scaling ability for queries. Take a look at the jsonnet changes to see how we are deploying this in our production setup. Keep an eye out for a blog post with more information on how the frontend works and more information on this exciting new feature.
In our quest to improve query performance, we discovered that gzip, while good for compression ratio, is not the best for speed. So we introduced the ability to select from several different compression algorithms:
We are currently testing out LZ4 and snappy, LZ4 seemed like a good fit however we found that it didn't always compress the same data to the same output which was causing some troubles for another important improvement:
Extending on the work done by @bboreham on Cortex, @pstibrany added a few new flags and code to synchronize chunks between ingesters, which reduces the number of chunks persisted to object stores and therefore also reduces the number of chunks loaded on queries and the amount of de-duplication work which needs to be done.
As mentioned above, LZ4 was in some cases compressing the same data with a different result which was interfering with this change, we are still investigating the cause of this issue (It may be in how we implemented something, or may be in the compression code itself). For now we have switched to snappy which has seen a reduction in data written to the object store from almost 3x the source data (with a replication factor of 3) to about 1.5x, saving a lot of duplicated log storage!
Another valuable change related to chunks:
With this change you can set a
chunk_target_sizeand Loki will attempt to fill a chunk to approx that size before flushing (previously a chunk size was a hard coded 10 blocks where the default block size is 262144 bytes). Larger chunks are beneficial for a few reasons, mainly on reducing API calls to your object store when performing queries, but also in reducing overhead in a few places, especially when processing very high volume log streams.Another big improvement is the introduction of accurate rate limiting when running microservices:
Previously the rate limit was applied at each distributor, however with traffic split over many distributors the limit would need to be adjusted accordingly. This meant that scaling up distributors required changing the limit. Now this information is communicated between distributors such that the limit should be applied accurately regardless of the number of distributors.
And last but not least on the notable changes list is a new feature for Promtail:
With this change Promtail can receive syslogs via TCP! Thanks to @bastjan for all the hard work on this submission!
Important things to note
-distributor.limiter-reload-periodflag / distributor'slimiter_reload_periodconfig option.All Changes
Once again we can't thank our community and contributors enough for the significant work that everyone is adding to Loki, the entire list of changes is long!!
Loki
Promtail
Fluent Bit
fluentd_threadlabel whenflush_thread_count> 1Fluentd
Docker Driver
Logcli
Helm
Jsonnet
Docs
Build
New Members
fluent/fluent-plugin-kafka (fluent-plugin-kafka)
v0.19.6Compare Source
v0.19.5Compare Source
awslabs/aws-fluent-plugin-kinesis (fluent-plugin-kinesis)
v3.7.0use_fips_endpointconfiguration parameter for FIPS-compliant endpoints : #227aggregated_record_sizeconfiguration parameter forkinesis_firehoseto reduce Firehose 5 KB per-record billing roundup : #193ProcessCredentialsinsecure string warning from newer aws-sdk-corev3.6.1v3.6.0Configuration
📅 Schedule: (UTC)
* 0-3 * * *)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.