apitech/loki - loki - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
Christian Haudum	f86d12f498	Update dskit to latest commit Diff: `b1b307db4f..3e308a4944` Signed-off-by: Christian Haudum <christian.haudum@gmail.com>	2 years ago
Periklis Tsirakidis	fb3ad058e0	operator: Update Loki operand to v2.7.1 (#7910 )	2 years ago
Maxim Ivanov	b773a7a3cf	promtail: ratelimiting by label (#7597 ) Limit stage can now takes optional `by_label_name` param, which tracks distinct values of that label and ratelimit entries independently. Log lines without expected label are not considered for ratelimiting and passed to the next pipeline stage.	2 years ago
Trevor Whitney	99b7c14e09	Prepare changelog and release notes for 2.7.1 (#7895 ) What this PR does / why we need it: Prepares changelog and release notes for 2.7.1 release. Co-authored-by: Dylan Guedes <djmgguedes@gmail.com>	2 years ago
Karsten Jeschkies	95ec710168	Introduce sizing tool to documentation page. (#7830 ) What this PR does / why we need it: The sizing tool should help to find a good cluster sizing when starting out with Loki. It's a dynamic form withing the documentation. ![image](https://user-images.githubusercontent.com/2418440/205147901-1fe86403-60af-4639-8ce3-9a192549900b.png) This pull request will be followed by help on hover. Special notes for your reviewer: Checklist - [ ] Reviewed the `CONTRIBUTING.md` guide - [x] Documentation added - [x] Tests updated - [ ] `CHANGELOG.md` updated - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md` Co-authored-by: Karsten Jeschkies <karste.jeschkies@grafana.com>	2 years ago
dependabot[bot]	655ab05b91	build(deps): bump golang.org/x/crypto from 0.1.0 to 0.4.0 (#7883 ) Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.1.0 to 0.4.0. <details> <summary>Commits</summary> <ul> <li><a href="`eb2c406296`"><code>eb2c406</code></a> go.mod: update golang.org/x dependencies</li> <li><a href="`2c476679df`"><code>2c47667</code></a> cryptobyte: add support for ReadASN1Integer into []byte</li> <li><a href="`0ec7e8322c`"><code>0ec7e83</code></a> internal/wycheproof: update Go 1.20 crypto/ecdh API</li> <li><a href="`6fad3dfc18`"><code>6fad3df</code></a> ssh: support rsa-sha2-256/512 on the server side</li> <li><a href="`21d60a1521`"><code>21d60a1</code></a> all: remove redundant type conversion</li> <li><a href="`183a9b70cc`"><code>183a9b7</code></a> go.mod: update golang.org/x dependencies</li> <li><a href="`334521b960`"><code>334521b</code></a> ssh: fix typo</li> <li><a href="`a3485e1740`"><code>a3485e1</code></a> all: use math/bits.RotateLeft</li> <li>See full diff in <a href="https://github.com/golang/crypto/compare/v0.1.0...v0.4.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=golang.org/x/crypto&package-manager=go_modules&previous-version=0.1.0&new-version=0.4.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2 years ago
Sandeep Sukhani	e9c93cd0f5	consider range and offset in queries while looking for schema config for query sharding (#7880 ) What this PR does / why we need it: We disable query sharding when a query touches multiple schema configs since they might have different sharding factors and might handle sharding differently. This check was done purely on the start and end time of the query without considering `range` and `offset`, which would change the length of the actual data being queried. Besides being incorrect, it also causes us to fail queries when migrating between tsdb and non-tsdb stores since both handle query sharding differently. For e.g., if the prev schema is `boltdb-shipper` and starting today, `tsdb` index is being used, so if we do a query `sum(rate({foo="bar"}[24h])` even with start and end within `tsdb` range, we will fail the query with error `incompatible index shard` if dynamic sharding goes with shard factor other than `32`(default shard factor in ingester for inverted index). The reason being the `range` here is `24h` which causes us to process data from previous schema as well. This PR takes care of the issue by factoring in `range` and `offset` in the queries while looking for schema config for query sharding. Checklist - [x] `CHANGELOG.md` updated	2 years ago
Leonardo Taccari	74906222c6	[helm] Release 3.6.1 to reintroduce PrometheusRule alerts (#7873 ) Commit `30caf142b2` introduced a regression ending up in generating no PrometheusRule alerts. That was fixed in commit `433d883fcd` but no releases were done. Bump version to have a release about it. What this PR does / why we need it: Which issue(s) this PR fixes: Should hopefully fix a request done by @xinbinhuang - who spotted and fixed this problem, thanks! - in #7860. I think it is important to tag a release ASAP because stopping having alerts can be a regression in possible production environments. Special notes for your reviewer: I have no idea if that will force to release a 3.6.1 Helm release without doing any tag or similar, sorry! I have tried to skim documentation about that and I have skimmed `.github/workflows/helm-release.yaml` and `grafana/helm-charts/.github/workflows/update-helm-repo.yaml@main` and I think that this will create a tag... but I'm not super-sure about that! If I've missed anything please let me know! Thanks! Checklist - [x] Reviewed the `CONTRIBUTING.md` guide - [ ] Documentation added - [ ] Tests updated - [x] `CHANGELOG.md` updated - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md`	2 years ago
dependabot[bot]	819112ba62	build(deps): bump cloud.google.com/go/bigtable from 1.3.0 to 1.18.1 (#7850 ) Bumps [cloud.google.com/go/bigtable](https://github.com/googleapis/google-cloud-go) from 1.3.0 to 1.18.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/googleapis/google-cloud-go/releases">cloud.google.com/go/bigtable's releases</a>.</em></p> <blockquote> <h2>bigtable: v1.18.1</h2> <h2><a href="https://github.com/googleapis/google-cloud-go/compare/bigtable/v1.18.0...bigtable/v1.18.1">1.18.1</a> (2022-12-02)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>bigtable:</strong> downgrade some dependencies (<a href="`754015236d`">7540152</a>)</li> </ul> <h2>bigtable: v1.18.0</h2> <h2><a href="https://github.com/googleapis/google-cloud-go/compare/bigtable/v1.17.0...bigtable/v1.18.0">1.18.0</a> (2022-11-10)</h2> <h3>Features</h3> <ul> <li><strong>bigtable:</strong> Add support for request stats (<a href="https://github-redirect.dependabot.com/googleapis/google-cloud-go/issues/6991">#6991</a>) (<a href="`609421e87f`">609421e</a>)</li> </ul> <h2>securitycenter: v1.17.0</h2> <h2><a href="https://github.com/googleapis/google-cloud-go/compare/securitycenter/v1.16.0...securitycenter/v1.17.0">1.17.0</a> (2022-11-16)</h2> <h3>Features</h3> <ul> <li><strong>securitycenter:</strong> Add files field to finding's list of attributes (<a href="`ac0c5c2122`">ac0c5c2</a>)</li> </ul> <h2>securitycenter: v1.16.0</h2> <h2><a href="https://github.com/googleapis/google-cloud-go/compare/securitycenter/v1.15.0...securitycenter/v1.16.0">1.16.0</a> (2022-11-03)</h2> <h3>Features</h3> <ul> <li><strong>securitycenter:</strong> rewrite signatures in terms of new location (<a href="`3c4b2b3456`">3c4b2b3</a>)</li> </ul> <h2>compute: v1.13.0</h2> <h2><a href="https://github.com/googleapis/google-cloud-go/compare/compute/v1.12.1...compute/v1.13.0">1.13.0</a> (2022-12-01)</h2> <h3>Features</h3> <ul> <li><strong>compute:</strong> start generating stubs dir (<a href="`5d0b405033`">5d0b405</a>)</li> <li><strong>compute:</strong> Update Compute Engine API to revision 20221101 (<a href="https://github-redirect.dependabot.com/googleapis/google-cloud-go/issues/751">#751</a>) (<a href="`7231644e71`">7231644</a>)</li> </ul> <h2>documentai: v1.13.0</h2> <h2><a href="https://github.com/googleapis/google-cloud-go/compare/documentai/v1.12.0...documentai/v1.13.0">1.13.0</a> (2022-12-01)</h2> <h3>Features</h3> <ul> <li><strong>documentai:</strong> added field_mask field in DocumentOutputConfig.GcsOutputConfig in document_io.proto (<a href="`2a0b1aeb16`">2a0b1ae</a>)</li> </ul> <h2>documentai: v1.12.0</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/googleapis/google-cloud-go/blob/main/documentai/CHANGES.md">cloud.google.com/go/bigtable's changelog</a>.</em></p> <blockquote> <h1>Changes</h1> <h2><a href="https://github.com/googleapis/google-cloud-go/compare/documentai/v1.12.0...documentai/v1.13.0">1.13.0</a> (2022-12-01)</h2> <h3>Features</h3> <ul> <li><strong>documentai:</strong> added field_mask field in DocumentOutputConfig.GcsOutputConfig in document_io.proto (<a href="`2a0b1aeb16`">2a0b1ae</a>)</li> </ul> <h2><a href="https://github.com/googleapis/google-cloud-go/compare/documentai/v1.11.0...documentai/v1.12.0">1.12.0</a> (2022-11-16)</h2> <h3>Features</h3> <ul> <li><strong>documentai:</strong> added TrainProcessorVersion, EvaluateProcessorVersion, GetEvaluation, and ListEvaluations v1beta3 APIs feat: added evaluation.proto feat: added document_schema field in ProcessorVersion processor.proto feat: added image_quality_scores field in Document.Page in document.proto feat: added font_family field in Document.Style in document.proto (<a href="`ac0c5c2122`">ac0c5c2</a>)</li> </ul> <h2><a href="https://github.com/googleapis/google-cloud-go/compare/documentai/v1.10.0...documentai/v1.11.0">1.11.0</a> (2022-11-09)</h2> <h3>Features</h3> <ul> <li><strong>documentai:</strong> added font_family to document.proto feat: added ImageQualityScores message to document.proto feat: added PropertyMetadata and EntityTypeMetadata to document_schema.proto (<a href="`9c5d6c857b`">9c5d6c8</a>)</li> </ul> <h2><a href="https://github.com/googleapis/google-cloud-go/compare/documentai/v1.9.0...documentai/v1.10.0">1.10.0</a> (2022-11-03)</h2> <h3>Features</h3> <ul> <li><strong>documentai:</strong> rewrite signatures in terms of new location (<a href="`3c4b2b3456`">3c4b2b3</a>)</li> </ul> <h2><a href="https://github.com/googleapis/google-cloud-go/compare/documentai/v1.8.0...documentai/v1.9.0">1.9.0</a> (2022-10-25)</h2> <h3>Features</h3> <ul> <li><strong>documentai:</strong> start generating stubs dir (<a href="`de2d18066d`">de2d180</a>)</li> </ul> <h2><a href="https://github.com/googleapis/google-cloud-go/compare/documentai/v1.7.0...documentai/v1.8.0">1.8.0</a> (2022-09-21)</h2> <h3>Features</h3> <ul> <li><strong>documentai:</strong> rewrite signatures in terms of new types for betas (<a href="`9f303f9efc`">9f303f9</a>)</li> </ul> <h2><a href="https://github.com/googleapis/google-cloud-go/compare/documentai/v1.6.0...documentai/v1.7.0">1.7.0</a> (2022-09-19)</h2> <h3>Features</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="`4ec9eed76b`"><code>4ec9eed</code></a> chore: release storage 1.18.1 (<a href="https://github-redirect.dependabot.com/googleapis/google-cloud-go/issues/4984">#4984</a>)</li> <li><a href="`e17334d1fe`"><code>e17334d</code></a> fix(storage): don't assume auth from a client option (<a href="https://github-redirect.dependabot.com/googleapis/google-cloud-go/issues/4982">#4982</a>)</li> <li><a href="`0f7457c6a9`"><code>0f7457c</code></a> chore(all): auto-regenerate gapics (<a href="https://github-redirect.dependabot.com/googleapis/google-cloud-go/issues/4977">#4977</a>)</li> <li><a href="`d28ba7868b`"><code>d28ba78</code></a> test(spanner): fix flaky TestIntegration_StartBackupOperation test (<a href="https://github-redirect.dependabot.com/googleapis/google-cloud-go/issues/4978">#4978</a>)</li> <li><a href="`5edfd3693b`"><code>5edfd36</code></a> chore: release spanner 1.26.0 (<a href="https://github-redirect.dependabot.com/googleapis/google-cloud-go/issues/4751">#4751</a>)</li> <li><a href="`090cc3ae0f`"><code>090cc3a</code></a> chore(all): auto-regenerate gapics (<a href="https://github-redirect.dependabot.com/googleapis/google-cloud-go/issues/4972">#4972</a>)</li> <li><a href="`acece394a3`"><code>acece39</code></a> chore(all): update all (<a href="https://github-redirect.dependabot.com/googleapis/google-cloud-go/issues/4971">#4971</a>)</li> <li><a href="`309b59e583`"><code>309b59e</code></a> fix(internal/godocfx): only put TOC status on mod if all pkgs have same statu...</li> <li><a href="`3441e1f1b6`"><code>3441e1f</code></a> test(bigtable): abbrviate instance and cluster names to avoid length overrun ...</li> <li><a href="`26dff4fca8`"><code>26dff4f</code></a> chore: release storage 1.18.0 (<a href="https://github-redirect.dependabot.com/googleapis/google-cloud-go/issues/4951">#4951</a>)</li> <li>Additional commits viewable in <a href="https://github.com/googleapis/google-cloud-go/compare/dlp/v1.3.0...storage/v1.18.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=cloud.google.com/go/bigtable&package-manager=go_modules&previous-version=1.3.0&new-version=1.18.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2 years ago
Rutger	17517bfea8	Promtail: Fix broken promtail-debug docker image (#7852 ) What this PR does / why we need it: The 'grafana/loki-build-image' version was not specified for the promtail-debug docker image, resulting in a ~6 month old 'latest' image as a build image. Updating this resulted in one more change: the newer version has a different location for the 'dlv' binary. The promtail-debug image would also hang waiting for a connection when ran, this adds the same flag, `--continue`, as added to the loki debug file in #1372. Special notes for your reviewer: I was interested in using the `-server.profiling_enabled=true` flag, to enable pprof endpoints, and scrape with phlare. This flag is not available in the non-debug version. Therefore I do not really care for attaching a debugger right away. Open to removing that change though. Checklist - [x] Reviewed the `CONTRIBUTING.md` guide - [ ] Documentation added - [ ] Tests updated - [ ] `CHANGELOG.md` updated - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md`	2 years ago
Felix Ehrenpfort	8423f56537	fix small typo (#7874 ) This change fixes a small typo in case of a missing space.	2 years ago
Chris James	527ee12220	Fixing a typo in configuration.md (#7878 ) What this PR does / why we need it: Fixes a typo in configuration.md, improves reader clarify and confidence Which issue(s) this PR fixes: Fixes #<issue number> Special notes for your reviewer: Checklist - [x] Reviewed the `CONTRIBUTING.md` guide - [ ] Documentation added - [ ] Tests updated - [ ] `CHANGELOG.md` updated - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md`	2 years ago
Steven Dungan	fee2374532	Update v2-7.md (#7857 )	3 years ago
Xinbin Huang	433d883fcd	Fix broken canary loki alerts (#7860 )	3 years ago
Mohamed-Amine Bouqsimi	03a34db8eb	Fix alertmanager per tenant override config behavior (#7805 ) Context: #7359 implement multi tenancy for the alertmanager config. However, the behavior of the per-tenant alertmanager config is erroneous, as it tries to merge the global alertmanager config with the per-tenant config. This does not work because there is no way of knowing if certain values were set by the user or if they were undefined and have the default Golang zero value (typically booleans). This PR changes the behavior of the alertmanager config to override all the configuration instead of trying to merge the global config with the per-tenant config. It also applies default values when appropriate.	3 years ago
Dylan Guedes	2e496ddff2	Loki: Add one additional bucket to `rate_store_stream_shards` (#7856 ) What this PR does / why we need it: Add one additional bucket (value=1) to the `rate_store_stream_shards`. By jumping from 0 to 2 we can't distinguish between streams that were minimally sharded (shards=2) to non-sharded ones (shards=1).	3 years ago
Robert Fratto	85392a9728	Update Prometheus dependency to latest release (v2.40.4) (#7826 ) Closes #7811, which is needed for Grafana Agent to update to v2.40 and add support for native histograms. I did not add support for native histograms to Loki, sorry :)	3 years ago
Robert Fratto	679c9e122f	rerun make drone so the newest build image is used (#7849 ) Follow up on #7848, where the Drone config needed to be updated as well	3 years ago
Robert Fratto	bd58352439	Update build image references to 0.25.0 (#7848 ) cc @slim-bean	3 years ago
Robert Fratto	da38da201a	loki-build-image: update faillint (#7841 ) faillint needs an update for Go 1.19 where it fails unexpectedly. First observed in #7826. See fatih/faillint#36	3 years ago
Travis Patterson	a1e9e4cdd0	Revert "Make some stream shard metrics per-tenant (#7838 )" (#7842 ) Because these metrics will be coming from each distributor, this is going to have an adverse impact on cardinality. Consider doing this with logging	3 years ago
Trevor Whitney	652e216a85	[helm] Bump helm Loki and GEL version (#7760 ) What this PR does / why we need it: Bumps Loki to 2.7.0 and GEL to 1.6.0 in the helm chart.	3 years ago
Travis Patterson	96fc2abfff	Make some stream shard metrics per-tenant (#7838 ) This PR just adds tenant information so some of our per-stream-rate-limit metrics.	3 years ago
Christian Haudum	feaf9c3232	Log query string on retry alongside the error (#7834 ) What this PR does / why we need it: For better observability of query retries. Signed-off-by: Christian Haudum <christian.haudum@gmail.com>	3 years ago
Kaviraj Kanagaraj	25f4dda811	fix(memcached): use `default` branch avoid writing to closed chan (#7833 ) Signed-off-by: Kaviraj <kavirajkanagaraj@gmail.com> What this PR does / why we need it: Follow up to https://github.com/grafana/loki/pull/7817 This PR uses `default` branch instead of `inputCh <- work` to make sure we are writing to closed `inputCh`. Gist is, `default` run [only when none of the branch is ready](https://go.dev/tour/concurrency/6). which makes more sense rather than to have `inputCh <- work` (writing to closed channel on the branch condition) These can be explained by these two tiny snippets. * [with `default`](https://go.dev/play/p/-FspbTZd20I) * [without `default`](https://go.dev/play/p/Ag4WznOaEq0) Which issue(s) this PR fixes: Fixes #NA Special notes for your reviewer: We already have test `TestMemcached_fetchKeysBatched` to catch this behaviour. In fact this test caught this probabilistic behaviour in some CI failures. [here ](https://drone.grafana.net/grafana/loki/17853/3/4) and[ here](https://drone.grafana.net/grafana/loki/17854/3/4) Thanks @DylanGuedes for catching this CI failures. Checklist Signed-off-by: Kaviraj <kavirajkanagaraj@gmail.com>	3 years ago
Trevor Whitney	37b1c0fce0	guard against divide by 0 when splitting parallelism (#7831 ) What this PR does / why we need it: Which issue(s) this PR fixes: We saw a spike in divide by zero panics in the code introduced in #7769. I was able to reproduce this error via a test that calculates `WeightedParallelism` with a start that's after the end. Not sure if this is possible, but we definitely saw this happening in our ops environment, so something is causing it, and the fix should guard against it in any case. Special notes for your reviewer: Checklist - [X] Tests updated Co-authored-by: Sandeep Sukhani <sandeep.d.sukhani@gmail.com>	3 years ago
cadrake	ea9ad336dc	Loki: Modified heroku drain target to make any url query parameters available as labels (#7619 ) What this PR does / why we need it: This PR reads the url query parameters included in Heroku drain POST request and creates `__param_<name>` labels similar to how the parameters work with prometheus metrics and metric endpoints as a way to allow setting the true application name when ingesting logs from a Heroku drain. Which issue(s) this PR fixes: Fixes #<issue number> Special notes for your reviewer: The existing `app` field coming from Heroku only specifies application source (either the application itself or Heroku) and thus is insufficient for uniquely identifying a log lines source. Checklist - [x] Reviewed the `CONTRIBUTING.md` guide - [x] Documentation added - [x] Tests updated - [x] `CHANGELOG.md` updated - [x] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md`	3 years ago
Travis Patterson	eb7fbfe0b4	Improve ratestore performance (#7810 ) This PR changes the Rate Store to use multi-level maps rather than `tenant+stream-fingerprint` key. Benchmarks: old ``` goos: linux goarch: amd64 pkg: github.com/grafana/loki/pkg/distributor cpu: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz BenchmarkRateStore-8 117 10420080 ns/op 3201761 B/op 200025 allocs/op PASS ok github.com/grafana/loki/pkg/distributor 14.646s ``` new ``` goos: linux goarch: amd64 pkg: github.com/grafana/loki/pkg/distributor cpu: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz BenchmarkRateStore-8 320 3811906 ns/op 2660 B/op 26 allocs/op ``` stats ``` name old time/op new time/op delta RateStore-8 10.7ms ± 8% 4.1ms ± 8% -61.42% (p=0.000 n=10+10) name old alloc/op new alloc/op delta RateStore-8 3.20MB ± 0% 0.00MB ± 0% -99.92% (p=0.000 n=8+9) name old allocs/op new allocs/op delta RateStore-8 200k ± 0% 0k ± 0% -99.99% (p=0.000 n=9+10) ```	3 years ago
李国忠	63a57c7b5c	[bugfix] scheduler: Gracefully shutdown querier when using query-scheduler (#7735 ) What this PR does / why we need it: Gracefully shutdown querier when using query-scheduler This PR is an attempt to fix a bug that my loki cluster is unavailable for logql. The source code and ideas are from mimir of LGTM. Thanks mimir and pr author @pracucci Which issue(s) this PR fixes: Fixes #7722 Special notes for your reviewer: mimir PR https://github.com/grafana/mimir/pull/1756 https://github.com/grafana/mimir/pull/1767 Checklist - [x] Reviewed the `CONTRIBUTING.md` guide - [ ] Documentation added - [x] Tests updated - [ ] `CHANGELOG.md` updated - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md` Co-authored-by: Karsten Jeschkies <k@jeschkies.xyz>	3 years ago
Kaviraj Kanagaraj	4efdc131be	fix(memcached): panic on `send on closed channel`. (#7817 )	3 years ago
Christian Simon	2ff6f13c8b	Better error message for empty selector queries (#6936 ) This improves the error when an empty label selector is given: Before: ```sh-session # Before $ logcli query "{}" Error response from server: parse error at line 1, col 2: syntax error: unexpected }, expecting IDENTIFIER # After $ logcli query "{}" Error response from server: parse error : queries require at least one regexp or equality matcher that does not have an empty-compatible value. For instance, app=~".*" does not meet this requirement, but app=~".+" will ``` I fear that might have wider implications, so it would be great to get a lot of eyes on this. In theory I think we should remove the restriction on querying all log streams, but this should maybe discussed in a follow up PR 🙂 Co-authored-by: Karsten Jeschkies <karsten.jeschkies@grafana.com>	3 years ago
Periklis Tsirakidis	54e6c19fc6	operator: Apply delete client changes for compat with release-2.7.x (#7815 )	3 years ago
Anders Bennedsgaard	b5563cee08	[Helm] Remove unused value and set default values explicitly (#7576 ) What this PR does / why we need it: `monitoring.alerts` are not used in the Loki Helm chart. This removes it. Furthermore, some values are referenced in the templates, but not used in the values file. This adds the default values. Which issue(s) this PR fixes: Fixes #7575 Special notes for your reviewer: https://github.com/AndersBennedsgaard/loki/blob/main/production/helm/loki/templates/single-binary/pdb.yaml#L15 should probably also be updated since `podDisruptionBudget` is not referenced in the values file. However, I am unsure what default values should be used. https://github.com/AndersBennedsgaard/loki/blob/main/production/helm/loki/templates/networkpolicy.yaml#L124 should probably also be updated since the `loki.rulerSelectorLabels` is not a valid helper function. However, I am unsure which selector labels to use. Especially since it seems like `ruler` is not used. Perhaps any reference to `ruler` should be removed? Checklist - [x] Reviewed the `CONTRIBUTING.md` guide - [x] Documentation added - [ ] Tests updated - [ ] `CHANGELOG.md` updated - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md`	3 years ago
Sandeep Sukhani	89d81020ce	fix lint issues from PR 7804 (#7814 ) What this PR does / why we need it: I had enabled auto-merge in PR #7804, but somehow it still merged the PR without all the checks passing. This PR fixes the failing lint and tests.	3 years ago
Jan-Otto Kröpke	5dc60567da	[Helm] Add support for azure blob storage (#7500 ) What this PR does / why we need it: Support Azure Blob Storage in helm chart. See https://grafana.com/docs/loki/latest/storage/#azure-storage-account-1 Which issue(s) this PR fixes: Special notes for your reviewer: Checklist - [ ] Reviewed the `CONTRIBUTING.md` guide - [x] Documentation added - [ ] Tests updated - [x] `CHANGELOG.md` updated - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md` Signed-off-by: Jan-Otto Kröpke <jok@cloudeteer.de>	3 years ago
Sandeep Sukhani	1410808ee9	use grpc for communicating with compactor for query time filtering of data requested for deletion (#7804 ) What this PR does / why we need it: Add grpc support to compactor for getting delete requests and gen number for query time filtering. Since these requests are internal to Loki, it would be good to use grpc instead of HTTP same as all the internal requests we do in Loki. I have added a new config for accepting the grpc address of the compactor. I tried having just the existing config and detecting if it is a grpc server, but it was hard to do it reliably, considering the different deployment modes we support. I think it is safe to keep it the same and eventually deprecate the existing config. Checklist - [x] Documentation added - [x] Tests updated - [x] `CHANGELOG.md` updated	3 years ago
George Tsilias	d3615f7e9e	promtail: Handle nil error on target Details() call (#7771 ) What this PR does / why we need it: This PR addresses issue [#6930](https://github.com/grafana/loki/issues/6930). Promtail should not panic when the Details() method is called for a target that has no errors. Which issue(s) this PR fixes: Fixes #6930	3 years ago
Kaviraj Kanagaraj	30ddd77150	loki-canary: respect `useTLS` flag when `push` mode is enabled. (#7701 ) What this PR does / why we need it: Currently `useTLS` flag is ignored on the push writer. This PR consider that flag and adjust the schema (http -> https) when that flag is enabled. Which issue(s) this PR fixes: Fixes #7692 Special notes for your reviewer: Checklist	3 years ago
Robert Jacob	6e217c6aa1	operator: Fix alert unit tests (#7812 ) What this PR does / why we need it: Fixes the Prometheus alert tests broken by #7809 Checklist - [x] Reviewed the `CONTRIBUTING.md` guide - [x] Tests updated	3 years ago
Josef Johansson	b05f4fced3	Remove hardwired '127.0.0.1' values in default addresses (#7784 ) While running all-in-one Loki instance, it's not possible to listen on anything other than IPv4 since compactor_address is then set to http://127.0.0.1. This enables listening on only IPv6. Also if frontend_address, scheduler_ring and scheduler_address is not set, the default value is to connect to '127.0.0.1:<grpc_listen_port>'. Which means that grpc_listen_address is ignored. What this PR does / why we need it: It's not possible to use compactor while using an all-in-one instance and listening to IPv6. Let's not ignore grpc_listen_address to not confuse users. Special notes for your reviewer: As noted in the first commit, the default behavior is changed from defaulting to `127.0.0.1` to `localhost`. Not sure how major that change is though. My /etc/hosts says ``` $ grep localhost /etc/hosts 127.0.0.1 localhost ``` Signed-off-by: Josef Johansson <josef@oderland.se>	3 years ago
Robert Jacob	4bcecefd05	operator: Fix histogram-based alerting rules (#7809 )	3 years ago
Robert Jacob	6d7d537518	operator: Replace fifocache usage by embedded_cache (#7808 )	3 years ago
Dylan Guedes	4567d01ac6	Loki: Add new sharding metrics (histogram based) (#7762 ) What this PR does / why we need it: Add histogram-version of two existing stream sharding metrics. The new metrics are: - `rate_store_stream_shards`: Will show us the distribution of shards reported by ingesters. This will help us on monitoring the number of shards we're dealing with. As of now we only have access to the max number of shards seen, which is helpful but not enough. - `rate_store_stream_rate_bytes`: Same as below: will help us understand the distribution of stream sizes instead of only showing us the max stream size seen.	3 years ago
Karsten Jeschkies	691b8be6c7	Provide Terraform script for setting up S3 and document role based access. (#7656 ) What this PR does / why we need it: Role based access to S3 on an EKS cluster via service account annotation was not documented well and let to some confusion. This change documents how a role based accessis achieved with providing an AWS secret access key and access key id. Thus there is no change of accidentally leaking credentials. A Terraform module is provided under `production/terraform/modules/s3` that provisions and S3 bucket and IAM role and policy. Which issue(s) this PR fixes: Fixes #7279 Special notes for your reviewer: Checklist - [ ] Reviewed the `CONTRIBUTING.md` guide - [x] Documentation added - [ ] Tests updated - [ ] `CHANGELOG.md` updated - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md` Co-authored-by: Pablo Angulo <pablo.angulo@grafana.com>	3 years ago
李国忠	6d05ade6a8	[performance] metrics query: range vector support streaming agg when no overlap (#7380 ) metrics query: range vector support streaming agg when no overlap	3 years ago
Paul Wheeler	85d6794d2b	fluent-bit: Update the Fluent Bit plugin README with correct golang minimum version (#7302 ) What this PR does / why we need it: The Loki plugin for Fluent Bit will not build with golang < 1.17 because of the use of net.IP.IsPrivate in the referenced version of github.com/grafana/dskit/netutil/netutil.go Which issue(s) this PR fixes: No issue exists (this is a minor documentation issue). Special notes for your reviewer: Checklist - [X] Reviewed the `CONTRIBUTING.md` guide - [N/A] Documentation added - [N/A] Tests updated - [N/A] `CHANGELOG.md` updated - [N/A] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md`	3 years ago
Periklis Tsirakidis	54d3e0e64e	operator: Check for mandatory CA configmap name in ObjectStorageTLS spec (#7753 )	3 years ago
Teddy Andrieux	217a914f98	helm/loki: Allow to override default loki `target` (#7791 ) What this PR does / why we need it: Add the ability to change the Loki `target` argument. E.g. one might want to use the single-binary which has target `all` but also the `table-manager` which is not part of it. So one can override the target with `all,table-manager`. Which issue(s) this PR fixes: Fixes #7788 Special notes for your reviewer: Checklist - [x] Reviewed the `CONTRIBUTING.md` guide - [x] `CHANGELOG.md` updated	3 years ago
Karsten Jeschkies	7ec51e8b9d	Log rule changes through API. (#7790 ) What this PR does / why we need it: This change should make it easier to detect changes to rules via the API. Which issue(s) this PR fixes: Fixes #7789 Special notes for your reviewer: Checklist - [ ] Reviewed the `CONTRIBUTING.md` guide - [ ] Documentation added - [ ] Tests updated - [ ] `CHANGELOG.md` updated - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md` Co-authored-by: Christian Haudum <christian.haudum@gmail.com>	3 years ago
MarNicGit	59c1abe259	Docs - Move PR's in CHANGELOG.md that weren't actually implemented in 2.7.x (#7690 ) Fixes the changelog. - PR #7462 and #7461 were not included in the 2.7.x release (they were submitted right after the cutoff and did not get backported) and accidentally ended up in the 2.7.x changelog. Moved them up to Main/Unreleased. - Moved #7602 to enhancements section of Promtail	3 years ago

... 5 6 7 8 9 ...

4607 Commits (ee0f46beed12f482032649966ece7fd1df7abdb5) All Branches Search

4607 Commits (ee0f46beed12f482032649966ece7fd1df7abdb5)

All Branches