Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update grafana/alloy docker tag to v1.3.1 (main) #9100

Merged
merged 1 commit into from
Aug 26, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 26, 2024

Mend Renovate

This PR contains the following updates:

Package Update Change
grafana/alloy minor v1.2.1 -> v1.3.1

Release Notes

grafana/alloy (grafana/alloy)

v1.3.1

Compare Source

Bugfixes
  • Changed the cluster startup behaviour, reverting to the previous logic where
    a failure to resolve cluster join peers results in the node creating its own cluster. This is
    to facilitate the process of bootstrapping a new cluster following user feedback (@​thampiotr)

  • Fix a memory leak which would occur any time loki.process had its configuration reloaded. (@​ptodev)

v1.3.0

Compare Source

Breaking changes
Breaking changes to non-GA functionality
  • Update Public preview remotecfg argument from metadata to attributes. (@​erikbaranowski)

  • The default value of the argument unmatched in the block routes of the component beyla.ebpf was changed from unset to heuristic (@​marctc)

Features
  • Added community components support, enabling community members to implement and maintain components. (@​wildum)

  • A new otelcol.exporter.debug component for printing OTel telemetry from
    other otelcol components to the console. (@​BarunKGP)

Enhancements
Bugfixes
  • Fixed a clustering mode issue where a fatal startup failure of the clustering service
    would exit the service silently, without also exiting the Alloy process. (@​thampiotr)

  • Fix a bug which prevented config reloads to work if a Loki metrics stage is in the pipeline.
    Previously, the reload would fail for loki.process without an error in the logs and the metrics
    from the metrics stage would get stuck at the same values. (@​ptodev)


Configuration

📅 Schedule: Branch creation - "before 9am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner August 26, 2024 08:01
@aknuds1 aknuds1 merged commit d6a4fce into main Aug 26, 2024
29 checks passed
@aknuds1 aknuds1 deleted the deps-update/main-grafana-alloy-1.x branch August 26, 2024 08:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant