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

Rule overview: Combine groups with same name #4317

Closed
tom932 opened this Issue Jun 27, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@tom932
Copy link

tom932 commented Jun 27, 2018

Proposal

My situation:

  • I have different alert rule-files for different user groups, so the groups can add their own alerting rules in their own files.
  • Some of them have similar alert groups, e.g. each group performs blackbox-checks on their services.
  • Therefore, each of the files contains a rule group blackbox with 1 to many alerts.

In the rule overview in the Web-UI, there are now several groups with the name blackbox (and others), each containing 1 to many alerting rules. It would be nice, if all those groups were combined to one group, due to the same name.

Environment

  • System information:

    Prometheus is running in official docker container

  • Prometheus version:

    v2.2.1 running in docker container

  • Alertmanager version:

    Not relevant, since prometheus feature request

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Jun 27, 2018

I don't see a way to make this work. A key property of rule groups is ordering, and there's no clear ordering across groups from different files.
Another key property is isolation, that one slow rule group from one team doesn't affect other rule groups. By silently combining rule groups just because they have the same name, users would lose that benefit.

If you wish to combine rule groups together, this would be best done via configuration management on your end.

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 22, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 22, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.