Skip to content

Conversation

@tobiaskohlbau
Copy link

@tobiaskohlbau tobiaskohlbau commented Nov 27, 2025

In case the job name is equal (for e.g. k8s-monitoring installation) multiple instances of alloy get deployed into a cluster alloy-logs, alloy-singleton which results in an alert firing for configuration drift. This CL addresses the issue by grouping together on the app label which matches alloy-logs and alloy-metrics in the case of k8s-monitoring.

Fixes #4945

PR Description

Which issue(s) this PR fixes

Notes to the Reviewer

This is only a proposed change, lets discuss the details in #4945 first and settle on the right solution.

PR Checklist

  • CHANGELOG.md updated
  • Documentation added
  • Tests updated
  • Config converters updated

In case the job name is equal (for e.g. k8s-monitoring installation)
multiple instances of alloy get deployed into a cluster alloy-logs,
alloy-singleton which results in an alert firing for configuration drift.
This CL addresses the issue by grouping together on the app label which
matches alloy-logs and alloy-metrics in the case of k8s-monitoring.

Fixes grafana#4945
@tobiaskohlbau tobiaskohlbau requested a review from a team as a code owner November 27, 2025 07:54
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

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.

alloy mixin alerting for cluster drift broken

2 participants