chore: Forwardport release/v1.13 to main#5627
Merged
Merged
Conversation
…ort] (#5545) ## Backport of #4300 This PR backports #4300 to release/v1.13. ### Original PR Author @clayton-cornell ### Description <!-- CONTRIBUTORS GUIDE: https://github.com/grafana/alloy/blob/main/docs/developer/contributing.md#updating-the-changelog If this is your first PR or you have not contributed in a while, we recommend taking the time to review the guide. It gives helpful instructions for contributors around things like how to update the changelog. --> #### PR Description Rework the Linux scenario doc to clarify and expand info #### Which issue(s) this PR fixes <!-- Uncomment the following line if you want that GitHub issue gets automatically closed after merging the PR --> <!-- Fixes #issue_id --> #### Notes to the Reviewer #### PR Checklist <!-- Remove items that do not apply. For completed items, change [ ] to [x]. --> - [ ] CHANGELOG.md updated - [ ] Documentation added - [ ] Tests updated - [ ] Config converters updated --- *This backport was created automatically.* Co-authored-by: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…rmissions [backport] (#5555) ## Backport of #5009 This PR backports #5009 to release/v1.13. ### Original PR Title docs: Update prometheus.exporter.cadvisor to add information about permissions ### Original PR Author @clayton-cornell ### Description This PR adds information about how to set permissions to run Alloy in local, Docker and K8s. It was compared against the related Issues, and compared against advice give in the Alloy forums. Fixes: * #990 * #3482 --- *This backport was created automatically.* Co-authored-by: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Piotr <17101802+thampiotr@users.noreply.github.com>
…ows component topic [backport] (#5561) ## Backport of #5361 This PR backports #5361 to release/v1.13. ### Original PR Author @clayton-cornell ### Description Improve the examples and general topic cleanup - focus on readability, gerund use, linting errors, typos, matching source args, etc. Fixes #3812 --- *This backport was created automatically.* Co-authored-by: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com>
## Backport of #5307 This PR backports #5307 to release/v1.13. ### Original PR Author @clayton-cornell ### Description Clean up the community component doc metadata and add links * Removed `stage: experimental` metadata line * Removed shared text element for "Experimental" * Added link to Community components docs in the shared text block for community contributions Other changes: * Removed some empty spaces at the end of lines, in tables, and empty lines in code samples * Formatted some table spacing * Fixed the status of `otel.receiver.promethus` * The `prometheus.go` file says `Stability: featuregate.StabilityGenerallyAvailable`, on line 34. Updated docs to state GA. * Line 136 in `prometheus.go` says `enableNativeHistograms = c.opts.MinStability.Permits(featuregate.StabilityPublicPreview)`. Updated note to state Public Preview flag is needed to enable this feature * Added a `debug_metrics` block to the Block documentaiton section because of line 49 in `prometheus.go` which states `DebugMetrics otelcolCfg.DebugMetricsArguments alloy:"debug_metrics,block,optional"` ## Not done: * Add community content owners to CODEOWNERS Fixes: #5168 --- *This backport was created automatically.* Co-authored-by: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
## Backport of #5219 This PR backports #5219 to release/v1.13. ### Original PR Title docs: Refactor the Alloy introduction topics ### Original PR Author @clayton-cornell ### Description Refactor the Alloy introduction topics and include a link to the introduction YouTube video. This is a full rewrite of the Introduction section with a strong focus on providing information for people who are completely new to Alloy. It attempts to provide non-developer-based information that could help in a decision to try Alloy. YouTube resources are here: https://github.com/grafana/Grafana-Alloy-for-Beginners ## Review the changes here: * https://deploy-preview-alloy-5219-zb444pucvq-vp.a.run.app/docs/alloy/latest/introduction/ * https://deploy-preview-alloy-5219-zb444pucvq-vp.a.run.app/docs/alloy/latest/introduction/why-alloy/ * https://deploy-preview-alloy-5219-zb444pucvq-vp.a.run.app/docs/alloy/latest/introduction/how-alloy-works/ * https://deploy-preview-alloy-5219-zb444pucvq-vp.a.run.app/docs/alloy/latest/introduction/requirements/ * https://deploy-preview-alloy-5219-zb444pucvq-vp.a.run.app/docs/alloy/latest/set-up/supported-platforms/ * https://deploy-preview-alloy-5219-zb444pucvq-vp.a.run.app/docs/alloy/latest/set-up/estimate-resource-usage/ * https://deploy-preview-alloy-5219-zb444pucvq-vp.a.run.app/docs/alloy/latest/reference/release-information/ Do the locations for supported platforms and estimate resource usage make sense? ### Original topic content for reference: * https://grafana.com/docs/alloy/latest/introduction/ --- *This backport was created automatically.* Co-authored-by: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
fix(pyroscope.ebpf): backport dotnet nibble map fix
…k to fix pg_settings (#5574) ### Brief description of Pull Request Update version of the grafana fork of postgres_exporter to include a fix for a panic with Cloud Sql Postgres in pg_settings collector. ### Pull Request Details The upstream fix is included in upstream postgres_exporter v0.19.0, which will be shipped with Alloy 1.14.0. This backport is targeted for Alloy 1.13. Fork patch: grafana/postgres_exporter#30 ### Issue(s) fixed by this Pull Request Fixes #5502 ### Notes to the Reviewer <!-- Add any relevant notes for the reviewers and testers of this PR. --> ### PR Checklist <!-- Remove items that do not apply. For completed items, change [ ] to [x]. --> - [ ] Documentation added - [ ] Tests updated - [ ] Config converters updated
…rt] (#5584) ## Backport of #5564 This PR backports #5564 to release/v1.13. ### Original PR Title docs(pyroscope.relabel): Clarify scope of `pyroscope.relabel` ### Original PR Author @jake-kramer ### Description Addresses confusion in #4689 --- *This backport was created automatically.* Co-authored-by: Jake Kramer <899428+jake-kramer@users.noreply.github.com> Co-authored-by: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com>
…secscontainermetrics` component [backport] (#5585) ## Backport of #5347 This PR backports #5347 to release/v1.13. ### Original PR Author @clayton-cornell ### Description Edit ECS tutorial to add new steps for the `otelcol.receiver.awsecscontainermetrics` component . Split tutorial into two paths... the original "stable" option and the new experimental `otelcol.receiver.awsecscontainermetrics` option. Clean up content: * fix bullets for consistency * fix the paths eg `/bin/bash` instead of just `bash` * removed some unused link definitions Fixes #4566 ### Note to reviewers I used AI to generate the configs. I do not have ECS to do any testing so I relied on AI to check the configuration examples. The configuration code snippets should be checked for validity and accuracy Preview for review is here: https://deploy-preview-alloy-5347-zb444pucvq-vp.a.run.app/docs/alloy/latest/collect/ecs-opentelemetry-data/ --- *This backport was created automatically.* Co-authored-by: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…5586) ## Backport of #5565 This PR backports #5565 to release/v1.13. ### Original PR Author @ptodev ### Description `otelcol.exporter.otlphttp` is what the Grafana databases and Grafana Cloud support. We should steer users towards that component so that they have a smoother onboarding experience. The reason why `otelcol.exporter.otlp` has been used so far is that historically Tempo only supported gRPC, and it was also the first Grafana DB to support OTel. Today Tempo supports HTTP, and Mimir and Loki only support HTTP OTLP. Related to #1310 --- *This backport was created automatically.* Co-authored-by: Paulin Todev <paulin.todev@gmail.com> Co-authored-by: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com>
## Backport of #5591 This PR backports #5591 to release/v1.13. ### Original PR Author @kalleep ### Description This should fix out issues with publishing new containers --- *This backport was created automatically.* Co-authored-by: Karl Persson <23356117+kalleep@users.noreply.github.com>
…rt] (#5614) ## Backport of #5606 This PR backports #5606 to release/v1.13. ### Original PR Author @thampiotr ### Description ### Brief description of Pull Request feat(otelcol): Expose missing tail_sampling drop and bytes_limiting options ### Pull Request Details Expose pre-existing missing tail sampling options and policy types in Alloy’s otelcol wrapper and docs. - Add `sample_on_first_match` and `drop_pending_traces_on_shutdown` to `otelcol.processor.tail_sampling` arguments and converter mapping. - Add `bytes_limiting` policy support (`bytes_per_second`, `burst_capacity`) across top-level policies and nested `and`, `drop`, and `composite` sub-policies. - Add `drop` policy support with `drop_sub_policy` blocks. - Update the component reference docs for new arguments, blocks, policy decisions, and example config. - Extend and update tail sampling tests and converter snapshots to cover the new options/policies. --- *This backport was created automatically.* Co-authored-by: Piotr <17101802+thampiotr@users.noreply.github.com>
## Backport of #5623 This PR backports #5623 to release/v1.13. ### Original PR Author @jharvey10 ### Description ### Brief description of Pull Request Fix the forwardport logic by pushing a temp branch and polling until the required zizmor check completes, then proceeding as per usual with the forwardport job. --- *This backport was created automatically.* Co-authored-by: Joe Harvey <51208233+jharvey10@users.noreply.github.com>
…5625) ## Backport of #5603 This PR backports #5603 to release/v1.13. ### Original PR Author @thampiotr ### Description ### Brief description of Pull Request release: publish rendered mixin dashboards as release asset ### Pull Request Details This PR configures GitHub Actions to publish the rendered mixin dashboards from `operations/alloy-mixin/rendered/dashboards/` as a zip archive in GitHub releases. Previously, these dashboards were only available in the source code. This change makes them easily downloadable as a release artifact, allowing users to fetch them all when importing to Grafana. Related #5074 --- *This backport was created automatically.* Co-authored-by: Piotr <17101802+thampiotr@users.noreply.github.com> Co-authored-by: Piotr <thampiotr@users.noreply.github.com>
🤖 I have created a release *beep* *boop* --- ## [1.13.2](v1.13.1...v1.13.2) (2026-02-23) ### Bug Fixes 🐛 * Expose missing `otelcol.processor.tail_sampling` options [backport] ([#5614](#5614)) ([3225ea3](3225ea3)) * **mixin:** Add zipped dashboards as a release artifact [backport] ([#5625](#5625)) ([37ff20f](37ff20f)) * **profiler:** Backport Go 1.26 gopclntab textStart fix ([#5572](#5572)) ([5ca05c9](5ca05c9)) * **prometheus.exporter.postgres:** Update version of the exporter fork to fix pg_settings ([#5574](#5574)) ([62a52f8](62a52f8)) * **pyroscope.ebpf:** Backport dotnet nibble map fix ([#5553](#5553)) ([6c62760](6c62760)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: grafana-alloybot[bot] <167359181+grafana-alloybot[bot]@users.noreply.github.com>
Forwardports the release/v1.13 branch to main after the v1.13 release. Triggered by release-please PR #5568: chore(release/v1.13): Release 1.13.2 This commit serves two purposes: 1. Records the release branch history (including tags) while keeping main's content unchanged 2. Syncs release-please changes (version bumps, changelog updates) with the main branch
Contributor
|
💻 Deploy preview deleted (chore: Forwardport release/v1.13 to main). |
Contributor
|
💻 Deploy preview deleted (chore: Forwardport release/v1.13 to main). |
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.
3 participants
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.
Automated forwardport. Triggered by release-please PR #5568.
Do not merge manually; the workflow will push to main after zizmor passes.