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

Commit Graph

Author	SHA1	Message	Date
nervo	65bef5c360	Helm: Fix components notes (#8194 ) Add component `backend` in the list of installed components on helm notes, based on `read.legacyReadTarget` value, just like backend statefulset.	2 years ago
Christian Haudum	d97aaca089	[docs] Clarify for what version the Helm chart docs are applicable (#8172 ) What this PR does / why we need it: The docs and reference of the Helm chart in the documentation is only applicable for the Loki Helm chart `>= 3.0` and therefore does not apply to the `grafana/loki-stack` chart, which depends on the Loki Helm chart `^2.15.2` ([requirements.yaml](https://github.com/grafana/helm-charts/blob/main/charts/loki-stack/requirements.yaml#L5)). Also added a headline to the "Install Loki using Helm" index page, because it looks awkward without, see screenshot. ![2023-01-17_20-28-52](https://user-images.githubusercontent.com/281260/212994261-f817f556-4cbf-454f-920f-875c5c085689.png) Which issue(s) this PR fixes: Fixes: #8152 Signed-off-by: Christian Haudum <christian.haudum@gmail.com>	2 years ago
Prabuddha Chakraborty	20627ad000	Helm: Add ingester config in helm values (#7733 ) What this PR does / why we need it: Allow configuring ingester config from helm values: https://grafana.com/docs/loki/latest/configuration/#ingester We wanted to change the default chunk_encoding, which right now not possible in the current values template. Co-authored-by: Trevor Whitney <trevorjwhitney@gmail.com>	2 years ago
TAY TS	94ee5a2930	Helm chart: Add enableServiceLinks (#7129 ) What this PR does / why we need it: This is to allow disable `enableServiceLinks` so that the service environments are not injected into the pods where in my scenario Loki is deployed in the same namespace as the Knative services resulted the Loki pod unable to start up due to too many service environment being injected. Reference issue for pod unable to startup due to too many services: https://github.com/kubernetes/kubernetes/issues/84539#issue-514261281 Co-authored-by: Trevor Whitney <trevorjwhitney@gmail.com>	2 years ago
Callum Styan	399eb097fd	Remove the stream lag metric. (#6324 ) Removes the stream lag metric since it's not possible to get a correct value and also not cause issues with metrics registration or collection until we have the WAL Signed-off-by: Callum Styan <callumstyan@gmail.com> Signed-off-by: Callum Styan <callumstyan@gmail.com> Co-authored-by: Travis Patterson <travis.patterson@grafana.com>	2 years ago
Owen Diehl	a7ea9c1422	Revert "fix(logql): remove __error_details__ label on drop __error__ or other way around" (#8200 ) Reverts grafana/loki#8150 I was talking with @adityacs about reverting this PR and found the following: Looking at why tests don’t keep `__error_details__` when `__error__` is dropped and I found this line of code: ```go // LabelsResult returns the LabelsResult from the builder. // No grouping is applied and the cache is used when possible. func (b *LabelsBuilder) LabelsResult() LabelsResult { // unchanged path. if len(b.del) == 0 && len(b.add) == 0 && b.err == "" { return b.currentResult } return b.toResult(b.labels()) }``` https://github.com/grafana/loki/blob/main/pkg/logql/log/labels.go#L314 We only add err details when err isn’t empty anyway, so I guess we’ll revert for simplicity but just keep the same functionality	2 years ago
Kaviraj Kanagaraj	5031ae1b4e	doc(promtail): Doc about how log rotate works with promtail. (#8096 ) Changes 1. Why log rotation matters? 2. Different components involving in reading, writing and rotating logs 3. Different types of log rotation. 4. How to configure log rotation effectively to work with promtail Fixes # Should resolve all confusions around log rotation errors with promtail Related: #7967 Signed-off-by: Kaviraj <kavirajkanagaraj@gmail.com>	2 years ago
openbob	af93f4a11e	Helm: Add Table Manager support to Loki helm chart (#8098 ) The Table Manager is a Loki component which takes care of creating a periodic table before its time period begins, and deleting it once its data time range exceeds the retention period. This PR is to add Table Manager support to the loki helm chart deployment as the current chart is based on the deprecated loki-simple-scalable chart that did not support Table Manager. Fixes #<6830>	2 years ago
Trevor Whitney	b6004050a6	[helm] Fix self-monitoring tenant secret (#8198 ) What this PR does / why we need it: https://github.com/grafana/loki/pull/8081 introduced a bug that caused the `provisioner` job to create an incorrect secret for the self-monitoring tenant used by the canary. This fixes that bug, as well as adding a readme on how to use the `helm-cluster` k3d env. Special notes for your reviewer: Checklist - [ ] Reviewed the [`CONTRIBUTING.md`](https://github.com/grafana/loki/blob/main/CONTRIBUTING.md) guide (required) - [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`	2 years ago
Owen Diehl	e4cbe50279	support single & double hyphen arguments in version printing (#8199 ) Small fix for an annoyance due special case parsing for the `version` flag. Previously we looked for `-version`, now we use the the flag library to support both `--version\|-version`	2 years ago
Herman	9a516ce813	[docs] fix dead link in the docker client documentation (#8196 ) What this PR does / why we need it: Just fixes a dead link in the docker client docs.	2 years ago
Aditya C S	cf23194d05	fix(logql): remove __error_details__ label on drop __error__ or other way around (#8150 )	2 years ago
dependabot[bot]	5cfd6a3c49	Bump github.com/spf13/afero from 1.9.2 to 1.9.3 (#8191 ) Bumps [github.com/spf13/afero](https://github.com/spf13/afero) from 1.9.2 to 1.9.3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/spf13/afero/releases">github.com/spf13/afero's releases</a>.</em></p> <blockquote> <h2>v1.9.3</h2> <h2>What's Changed</h2> <ul> <li>Fix concurrency issue in MemMapFs.Mkdir/MkdirAll by <a href="https://github.com/bep"><code>@bep</code></a> in <a href="https://github-redirect.dependabot.com/spf13/afero/pull/379">spf13/afero#379</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/spf13/afero/compare/v1.9.2...v1.9.3">https://github.com/spf13/afero/compare/v1.9.2...v1.9.3</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="`a800a9de53`"><code>a800a9d</code></a> Fix concurrency issue in MemMapFs.Mkdir/MkdirAll</li> <li>See full diff in <a href="https://github.com/spf13/afero/compare/v1.9.2...v1.9.3">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=github.com/spf13/afero&package-manager=go_modules&previous-version=1.9.2&new-version=1.9.3)](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
Michel Hollands	cac2a131c9	Do not run release stage when check stage fails (#8175 )	2 years ago
Mohamed-Amine Bouqsimi	86a1feb2c1	operator: Add watch on the Alertmanager in OCP's user-workload-monitoring namespace (#8038 )	2 years ago
Ashwanth	0723678573	limits: add tenant to log lines for per-stream rate-limited and out-of-order errors (#8177 )	2 years ago
Karsten Jeschkies	f24da4a194	Display replicas, cores and nodes in sizing tool. (#8088 ) What this PR does / why we need it: No every users wants to deploy Loki with Helm. That's why we are going to display the required replicas as well. ![image](https://user-images.githubusercontent.com/2418440/212642958-17bc3fcd-0f6a-4ea8-8366-a3c28ddc6622.png) This change also fixes two bugs in the algorithm and introduces some tests for its invariant. 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` Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Kaviraj <kavirajkanagaraj@gmail.com> Signed-off-by: Danny Kopping <danny.kopping@grafana.com> Signed-off-by: Ashwanth Goli <iamashwanth@gmail.com> Co-authored-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Danny Kopping <danny.kopping@grafana.com> Co-authored-by: Kaviraj Kanagaraj <kavirajkanagaraj@gmail.com> Co-authored-by: liam-howe-maersk <118169897+liam-howe-maersk@users.noreply.github.com> Co-authored-by: JordanRushing <rushing.jordan@gmail.com> Co-authored-by: Trevor Whitney <trevorjwhitney@gmail.com> Co-authored-by: Periklis Tsirakidis <periklis@redhat.com> Co-authored-by: Ashwanth Goli <iamashwanth@gmail.com>	2 years ago
Trevor Whitney	da76b1394d	fix broken drone image for arm builds (#8186 ) What this PR does / why we need it: Harness pushed a bad drone image, causing the build to fail for all arm images. The build is currently failing on `main`, this should fix it. Signed-off-by: Ashwanth Goli <iamashwanth@gmail.com> Co-authored-by: Ashwanth Goli <iamashwanth@gmail.com>	2 years ago
Periklis Tsirakidis	664ea78154	operator: Remove custom webhook cert mounts for OLM-based deployment (#8173 )	2 years ago
Trevor Whitney	eb39e2645f	[helm] allow provisioned tokens to be created in different namespaces (#8081 ) What this PR does / why we need it: _Note_: This PR bumps the chart to 4.0, so it includes a few other breaking changes we've been waiting to make. The new helm chart has a few different ways to create tokens when running in enterprise mode: * The tokengen job creates the initial admin token * The provisioner job creates the self-monitoring tenant if enabled * The provisioner job can also create additional tenants if configured The problem with these jobs is they put the generated read/write tokens for these tenants in secrets in the same namespace as the loki deploiyment. This is problematic if you need these tokens for a specific application, for example a Grafana datasource, that is deployed in a separate namespace. This PR introduces two breaking changes, one of which is breaking as it significantly changes how both the self monitoring and additional tenants are configured. First it adds the value `enterprise.adminToken.additionalNamespaces` and moves `enterprise.adminTokenSecret` to `enterprise.adminToken.secret`. If `additionalNamespaces` are included, additional secrets containing the GEL admin token are created in those namespaces as well as the release namespace. Second, it changes the structure of defining a tenant from just a string name, to an object containing a `name` and `secretNamespace` field. The `secretNamespace` is the namespace the secret containing that tenants token(s) will be placed in. In the case of the self-monitoring token, a secret will still be created in the default namespace in addition to the `secretNamespace` specified as that token is required by multiple components.	2 years ago
JordanRushing	d8a0c6f87f	Revert "[loki-canary] Support passing loki address as environment variable (#8024 )" (#8183 ) What this PR does / why we need it: This PR reverts commit `f9ed9cb7d9` which introduced breaking config changes for the Loki canary. The relevant change introduced support for configuring a new `LOKI_ADDRESS` canary environment variable by adopting a new library for flags. This is the easiest path forward to avoid forcing breaking config changes on canary operators; such a change is likely better suited to join other configuration changes in a future major Loki release. Which issue(s) this PR fixes: N/A Special notes for your reviewer: Related PR: - https://github.com/grafana/loki/pull/8024 Checklist - [x] Reviewed the [`CONTRIBUTING.md`](https://github.com/grafana/loki/blob/main/CONTRIBUTING.md) guide (required) - [ ] 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
liam-howe-maersk	4681f9f487	Alerts: Exclude '/schedulerpb.SchedulerForQuerier/QuerierLoop' route in LokiRequestLatency alert (#8138 ) Excludes the route `/schedulerpb.SchedulerForQuerier/QuerierLoop` from the `LokiRequestLatency` alert query config. We have found that this route often has extremely high request latencies which will trigger the alert constantly for us. Looking through the source code it seems like it is expected to have high request latencies for this route and so in our configuration have excluded the route. We can see that this route is also being excluded in the [respective mimir config](https://github.com/grafana/mimir/blob/main/operations/mimir-mixin-compiled/alerts.yaml#L33) so believe it might be relevant to exclude here in loki as well	2 years ago
dependabot[bot]	70997fd090	Bump github.com/imdario/mergo from 0.3.12 to 0.3.13 (#8176 ) Bumps [github.com/imdario/mergo](https://github.com/imdario/mergo) from 0.3.12 to 0.3.13. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/imdario/mergo/releases">github.com/imdario/mergo's releases</a>.</em></p> <blockquote> <h2>Merging same-type slices supported, YAML upgraded to v3 (only used in tests), and more flexibility for transformers</h2> <h2>What's Changed</h2> <ul> <li>Fix typo in README.md by <a href="https://github.com/eltociear"><code>@eltociear</code></a> in <a href="https://github-redirect.dependabot.com/imdario/mergo/pull/184">imdario/mergo#184</a></li> <li>Adding StructBot to Mergo in the wild section by <a href="https://github.com/tjpnz"><code>@tjpnz</code></a> in <a href="https://github-redirect.dependabot.com/imdario/mergo/pull/193">imdario/mergo#193</a></li> <li>Add Goreleaser to featured projects by <a href="https://github.com/marcauberer"><code>@marcauberer</code></a> in <a href="https://github-redirect.dependabot.com/imdario/mergo/pull/191">imdario/mergo#191</a></li> <li>fix: gate transformers on valid non-nil destinations by <a href="https://github.com/zaquestion"><code>@zaquestion</code></a> in <a href="https://github-redirect.dependabot.com/imdario/mergo/pull/211">imdario/mergo#211</a></li> <li>Support slices of same type by <a href="https://github.com/heaths"><code>@heaths</code></a> in <a href="https://github-redirect.dependabot.com/imdario/mergo/pull/210">imdario/mergo#210</a></li> <li>Upgrade yaml to v3 by <a href="https://github.com/imdario"><code>@imdario</code></a> in <a href="https://github-redirect.dependabot.com/imdario/mergo/pull/212">imdario/mergo#212</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/eltociear"><code>@eltociear</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/imdario/mergo/pull/184">imdario/mergo#184</a></li> <li><a href="https://github.com/tjpnz"><code>@tjpnz</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/imdario/mergo/pull/193">imdario/mergo#193</a></li> <li><a href="https://github.com/marcauberer"><code>@marcauberer</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/imdario/mergo/pull/191">imdario/mergo#191</a></li> <li><a href="https://github.com/zaquestion"><code>@zaquestion</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/imdario/mergo/pull/211">imdario/mergo#211</a></li> <li><a href="https://github.com/heaths"><code>@heaths</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/imdario/mergo/pull/210">imdario/mergo#210</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/imdario/mergo/compare/0.3.12...v0.3.13">https://github.com/imdario/mergo/compare/0.3.12...v0.3.13</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="`1949787570`"><code>1949787</code></a> Update README.md</li> <li><a href="`80c13e16e7`"><code>80c13e1</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/imdario/mergo/issues/212">#212</a> from imdario/dcc/issue-206</li> <li><a href="`f86e6f60b7`"><code>f86e6f6</code></a> Upgrade yaml to v3</li> <li><a href="`39ebbbb298`"><code>39ebbbb</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/imdario/mergo/issues/210">#210</a> from heaths/issue209</li> <li><a href="`fd7d2bcdb0`"><code>fd7d2bc</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/imdario/mergo/issues/211">#211</a> from zaquestion/transformer_valid_destination</li> <li><a href="`8109749b3e`"><code>8109749</code></a> add test for deepMerge panic</li> <li><a href="`4bed36ec55`"><code>4bed36e</code></a> add test for keeping zero values with transformer</li> <li><a href="`ab6b2707a1`"><code>ab6b270</code></a> fix: gate transformers on valid non-nil destinations</li> <li><a href="`200f90d970`"><code>200f90d</code></a> Support slices of same type</li> <li><a href="`fd3dfc91a2`"><code>fd3dfc9</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/imdario/mergo/issues/191">#191</a> from marcauberer/master</li> <li>Additional commits viewable in <a href="https://github.com/imdario/mergo/compare/0.3.12...v0.3.13">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=github.com/imdario/mergo&package-manager=go_modules&previous-version=0.3.12&new-version=0.3.13)](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
Danny Kopping	4e16ea6b4d	Minor LID fixes (#8167 ) Signed-off-by: Danny Kopping <danny.kopping@grafana.com>	2 years ago
Kaviraj Kanagaraj	2597429c89	promtail: Add `max-line-size` limit to drop on client side (#8153 )	2 years ago
Kaviraj Kanagaraj	9b5fa5e100	doc(distributor): Clarify `distributor.max-line-size` flag. (#8165 ) What this PR does / why we need it: Add a clarrification of two flags `distributor.max-line-size` and `distributor.max-line-size-truncate`. And clarity on [discarding the logs](https://github.com/grafana/loki/blob/main/pkg/distributor/validator.go#L84-L92) if later is disabled while still former is set to non-zero values. Whereas if `distributor.max-line-size-truncate` is set, [log line is only truncated.](https://github.com/grafana/loki/blob/main/pkg/distributor/distributor.go#L517-L534) Signed-off-by: Kaviraj <kavirajkanagaraj@gmail.com> Which issue(s) this PR fixes: Fixes #NA Special notes for your reviewer: Figured while working on PR #8153 Checklist - [x] Reviewed the [`CONTRIBUTING.md`](https://github.com/grafana/loki/blob/main/CONTRIBUTING.md) guide (required) - [x] Documentation added Signed-off-by: Kaviraj <kavirajkanagaraj@gmail.com>	2 years ago
Danny Kopping	7c78d7ea44	Removing "replace" directive for line-buffered logger (#8162 )	2 years ago
dependabot[bot]	36907a81dd	Bump golang.org/x/time from 0.1.0 to 0.3.0 (#8161 ) Bumps [golang.org/x/time](https://github.com/golang/time) from 0.1.0 to 0.3.0. <details> <summary>Commits</summary> <ul> <li><a href="`2c09566ef1`"><code>2c09566</code></a> rate: the state of the limiter should not be changed when the requests failed</li> <li><a href="`80b9fac54d`"><code>80b9fac</code></a> x/time/rate: add rate.Sometimes, which runs a function occasionally.</li> <li>See full diff in <a href="https://github.com/golang/time/compare/v0.1.0...v0.3.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=golang.org/x/time&package-manager=go_modules&previous-version=0.1.0&new-version=0.3.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
Karsten Jeschkies	17fdfcbaa1	Emit help message when check-mod fails (#8157 )	2 years ago
dependabot[bot]	a8a4ba742d	Bump github.com/Masterminds/sprig/v3 from 3.2.2 to 3.2.3 (#8159 ) Bumps [github.com/Masterminds/sprig/v3](https://github.com/Masterminds/sprig) from 3.2.2 to 3.2.3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/Masterminds/sprig/releases">github.com/Masterminds/sprig/v3's releases</a>.</em></p> <blockquote> <h2>v3.2.3</h2> <h2>Changed</h2> <ul> <li>Updated docs (thanks <a href="https://github.com/book987"><code>@book987</code></a> <a href="https://github.com/aJetHorn"><code>@aJetHorn</code></a> <a href="https://github.com/neelayu"><code>@neelayu</code></a> <a href="https://github.com/pellizzetti"><code>@pellizzetti</code></a> <a href="https://github.com/apricote"><code>@apricote</code></a> <a href="https://github.com/SaigyoujiYuyuko233"><code>@SaigyoujiYuyuko233</code></a> <a href="https://github.com/AlekSi"><code>@AlekSi</code></a>)</li> <li><a href="https://github-redirect.dependabot.com/Masterminds/sprig/issues/348">#348</a>: Updated huandu/xstrings which fixed a snake case bug (thanks <a href="https://github.com/yxxhero"><code>@yxxhero</code></a>)</li> <li><a href="https://github-redirect.dependabot.com/Masterminds/sprig/issues/353">#353</a>: Updated masterminds/semver which included bug fixes</li> <li><a href="https://github-redirect.dependabot.com/Masterminds/sprig/issues/354">#354</a>: Updated golang.org/x/crypto which included bug fixes</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Masterminds/sprig/blob/master/CHANGELOG.md">github.com/Masterminds/sprig/v3's changelog</a>.</em></p> <blockquote> <h2>Release 3.2.3 (2022-11-29)</h2> <h3>Changed</h3> <ul> <li>Updated docs (thanks <a href="https://github.com/book987"><code>@book987</code></a> <a href="https://github.com/aJetHorn"><code>@aJetHorn</code></a> <a href="https://github.com/neelayu"><code>@neelayu</code></a> <a href="https://github.com/pellizzetti"><code>@pellizzetti</code></a> <a href="https://github.com/apricote"><code>@apricote</code></a> <a href="https://github.com/SaigyoujiYuyuko233"><code>@SaigyoujiYuyuko233</code></a> <a href="https://github.com/AlekSi"><code>@AlekSi</code></a>)</li> <li><a href="https://github-redirect.dependabot.com/Masterminds/sprig/issues/348">#348</a>: Updated huandu/xstrings which fixed a snake case bug (thanks <a href="https://github.com/yxxhero"><code>@yxxhero</code></a>)</li> <li><a href="https://github-redirect.dependabot.com/Masterminds/sprig/issues/353">#353</a>: Updated masterminds/semver which included bug fixes</li> <li><a href="https://github-redirect.dependabot.com/Masterminds/sprig/issues/354">#354</a>: Updated golang.org/x/crypto which included bug fixes</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="`581758eb7d`"><code>581758e</code></a> Updating the changelog for the 3.2.3 release</li> <li><a href="`5787448a04`"><code>5787448</code></a> Updating changelog for 3.2.2 release</li> <li><a href="`8489c3eb22`"><code>8489c3e</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/Masterminds/sprig/issues/354">#354</a> from mattfarina/bump-crypto-v0.3.0</li> <li><a href="`42ac6ac131`"><code>42ac6ac</code></a> Updating crypto library</li> <li><a href="`d65147bc88`"><code>d65147b</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/Masterminds/sprig/issues/353">#353</a> from mattfarina/bump-semver-3.2.0</li> <li><a href="`92ac1aee6a`"><code>92ac1ae</code></a> Updating semver package</li> <li><a href="`ce20d69f9f`"><code>ce20d69</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/Masterminds/sprig/issues/313">#313</a> from book987/master</li> <li><a href="`f9a478a510`"><code>f9a478a</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/Masterminds/sprig/issues/334">#334</a> from aJetHorn/patch-1</li> <li><a href="`58a4f651e0`"><code>58a4f65</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/Masterminds/sprig/issues/349">#349</a> from mattfarina/bump-go-19</li> <li><a href="`32424cc260`"><code>32424cc</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/Masterminds/sprig/issues/347">#347</a> from neelayu/patch-1</li> <li>Additional commits viewable in <a href="https://github.com/Masterminds/sprig/compare/v3.2.2...v3.2.3">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=github.com/Masterminds/sprig/v3&package-manager=go_modules&previous-version=3.2.2&new-version=3.2.3)](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
Dimitar Dimitrov	723f524e3b	Fix link to CONTRIUTING.md in PR template (#8156 ) The previous link lead to https://github.com/grafana/loki/CONTRIBUTING.md which doesn't exist.	2 years ago
Dimitar Dimitrov	6ea5a8e497	Update vendored dskit (#8155 ) What this PR does / why we need it: The Changelog diff between the two commits is `3e308a4944...7242706251` ``` * [CHANGE] Cache: Switch Memcached backend to use `github.com/grafana/gomemcache` repository instead of `github.com/bradfitz/gomemcache`. #248 * [ENHANCEMENT] Add cache, gate and stringsutil packages. #239 * [ENHANCEMENT] Cache: add Redis support. #245 * [ENHANCEMENT] Cache: Add the ability to use a custom memory allocator for cache results. #249 * [BUGFIX] Memberlist: fix crash when methods from `memberlist.Delegate` interface are called on `memberlist.KV` before the service is fully started. #244 ``` Checklist* - [x] Reviewed the [`CONTRIBUTING.md`](../CONTRIBUTING.md) guide (required) - 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`	2 years ago
Luis Felipe Vaca	d317e659c7	lambda-promtail-: fix parse kinesis timestamp (#7158 )	2 years ago
Owen Diehl	07487cd89d	fixes bug with queryIngesterWithin logic in asyncStore ingester stats… (#8145 ) Fixes a previous mistake in the logic calculating when to skip querying ingesters in the async store Statistics method. Notably `through.After` should be `through.Before` when skipping querying ingesters as that's when there's no overlap with the `query-ingesters-within` period: ```go // OLD CODE BELOW if a.queryIngestersWithin != 0 { // don't query ingesters if the query does not overlap with queryIngestersWithin. if !through.After(model.Now().Add(-a.queryIngestersWithin)) { // <----- should be through.Before return a.Store.Stats(ctx, userID, from, through, matchers...) } } ``` I discovered the problem while debugging querier OOMs during a boltdb-shipper -> tsdb migration and ultimately found this happened under the following circumstances: * Queries over high volumes of _recent_ data wouldn't query ingesters for index metadata * Without index metadata, we only checked storage metadata * There is a delay before we ship the index to storage, meaning we don't see it if ingesters are skipped * Calculating ideal shard factors without recent data for queries that only touch recent data _dramatically_ underestimates the desired shard factor * Queries aren't split enough and get scheduled onto too few querier replicas * They oom. We had some fun examples like a single replica trying to download 419,000 chunks/query To be clear, this is still a hypothesis, but a plausible one, especially after finding the boolean logic error this PR fixes. Instead of changing this one line, I took the opportunity to refactor this into a shared utility used by our other `GetChunkRefs` method which is already tested, ensuring the logic works as expected. I also added some more logging visibility into this code so we can understand what the difference is when querying statistics from storage vs ingesters. Finally, I added a helper to prepare our `Stats` objects to be logged which is now used in a few places.	2 years ago
Travis Patterson	5e53303cb8	run 'make doc' and commit the changes (#8142 )	2 years ago
Raphael Deem	63811f9025	Update README.md (#7799 )	2 years ago
Philipp Trulson	8edf8f9700	Helm: Use image tag for version labels in kubernetes resources (#8135 ) What this PR does / why we need it: This PR makes sure that the value of the `app.kubernetes.io/version` label in Kubernetes is the same as the image tag for Loki when set instead of always pinning it to the hardcoded `AppVersion` of the chart. Which issue(s) this PR fixes: Fixes #8077 Special notes for your reviewer: None Checklist - [x] Reviewed the [`CONTRIBUTING.md`](../CONTRIBUTING.md) guide (required) - [ ] 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
saurabhsadhale	c4091c83f4	operator: Fix docs for OpenShift Data Foundation storage uses bucketnames instead of bucketname (#8139 )	2 years ago
Ludovic Cleroux	6e3b62bf3e	Documentation: Add installation instructions for Istio (#4812 ) What this PR does / why we need it: Because there is very little information on how to install loki in the istio service mesh, and I spent a good deal of time figuring it out. Co-authored-by: Owen Diehl <ow.diehl@gmail.com>	2 years ago
Irina	5eba028656	Move to fork github.com/grafana/cloudflare-go (#8133 ) What this PR does / why we need it: The PR https://github.com/cloudflare/cloudflare-go/pull/743 to the upstream repo https://github.com/cloudflare/cloudflare-go was closed with the resolution: > We've spoken to the Grafana Loki team and they'll be building out an integration with Logpush so I don't think this is needed from their side anymore. I [spoke](https://raintank-corp.slack.com/archives/C9T1FLN9K/p1666293494583359) to Loki team and found out that moving to Logpush is not on the shortlist plan right now. I suggest moving to [github.com/grafana/cloudflare-go](https://github.com/grafana/cloudflare-go) fork as the main dependency to get rid of replacement directive. `02e0b3ae89/go.mod (L320)` Another point is replace directives complicate using loki as a dependency in other packages because replace directives should be moved to the upstream package as well. In general, replace was designed as a temporary solution to test code. It shouldn't be used permanently. Which issue(s) this PR fixes: Fixes https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/16722, https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/16453 Special notes for your reviewer: Checklist - [x] Reviewed the [`CONTRIBUTING.md`](../CONTRIBUTING.md) guide (required) - [ ] 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
dependabot[bot]	1760653e37	Bump github.com/prometheus/common from 0.38.0 to 0.39.0 (#8134 ) Bumps [github.com/prometheus/common](https://github.com/prometheus/common) from 0.38.0 to 0.39.0. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2 years ago
Christophe Collot	ec33a891df	lambda-promtail: remove duplicate key in terraform config sample (#8137 ) What this PR does / why we need it: This PR removes a duplicate key in the terraform configuration sample Which issue(s) this PR fixes: None Special notes for your reviewer: This is a trivial PR	2 years ago
Callum Styan	2c2f4914f6	[jsonnet] port some common jsonnet for statefulset and ingester creation (#7039 ) The mimir team turned a lot of jsonnet deployment code/config into functions. The functions make common config across deployments/statefulsets easier, and also creation of new similar but slightly different deployments/statefulsets of exsting components simpler as well. For example, it will make zone aware ingester creation simpler. The current changeset should (as in I tested it via `tk diff`) result in no diff for our own environments. Note that this is just ingester related, there's plenty of other nice jsonnet things the mimir team is doing that we could also copy. Signed-off-by: Callum Styan <callumstyan@gmail.com> Signed-off-by: Callum Styan <callumstyan@gmail.com>	2 years ago
Nils	e4fbd3c949	Loki: Add support for Azure Workload Identity authentication (#7540 )	2 years ago
youngpablo	ce09aac46d	resolves #5950 (input header error) (#7829 ) this PR fix error while parsing logs from containers with tty: true https://pkg.go.dev/github.com/docker/docker/client#Client.ContainerLogs like in docs: >if the container is using a TTY, there is only a single stream (stdout), and data is copied directly from the container output stream, no extra multiplexing or headers. cause of it we dont need to use StdCopy and can just write to StdOut Fixes #5950 thanks for help @scripter-v Co-authored-by: Karsten Jeschkies <k@jeschkies.xyz> Co-authored-by: Karsten Jeschkies <karsten.jeschkies@grafana.com>	2 years ago
Marcus Teixeira	78c2063e0b	Docs: fix helm ssd typo (#7959 ) Fix docs about helm ssd installation. Co-authored-by: Travis Patterson <travis.patterson@grafana.com>	2 years ago
Sandeep Sukhani	dfff86f1cd	skip compacting tables that do not fit in start and end date of desired schema config (#8127 ) Before compacting tables, we look up the schema config for them. If we do not find a schema config for a table, we skip them. However, the schema lookup code was considering the start time of the schema and not the end time. This can cause the compactor to try compacting tables with the same prefix as one of the previous schemas, but the table interval falls into one of the subsequent schemas with a different config. This PR fixes the issue and simplifies the code by reusing existing schema lookup code. I have also updated test cases to verify the fix works.	2 years ago
Karsten Jeschkies	4504ed2701	Cross build Promtail for ARM with journald support. (#8131 ) This is the follow up to #8111 and adds journald support for Promatil ARM and ARM64 builds. I've tested it locally with my Raspberry Pi and it works. Fixes #1459	2 years ago
Dbzman	cd1ba1911e	Fix labels for alerts (#7886 ) This fixes wrong labels for the LokiCanaryLatency alert and introduces "cluster" as label for LokiTooManyCompactorsRunning to be able to have multiple loki instances in the same namespace. documented in `docs/sources/upgrading/_index.md`	2 years ago
Guillaume Coué	802b337c63	Update README.md (#8132 ) What this PR does / why we need it: Updates docker diagram after changes in #8019 Signed-off-by: Danny Kopping <danny.kopping@grafana.com> Co-authored-by: Danny Kopping <danny.kopping@grafana.com>	2 years ago

1 2 3 4 5 ...

4526 Commits (3472aece09cfa1f0b35a613f72b3476a98b0f0bc) All Branches Search

4526 Commits (3472aece09cfa1f0b35a613f72b3476a98b0f0bc)

All Branches