You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add support for RabbitMQ alerting without depending on Prometheus Operator (#676)
* Integrate RabbitMQ Alerting without Prometheus Operator
Before this commit, RabbitMQ Alerting was set up with the assumption
that Prometheus Operator is installed.
However, many K8s clusters have Prometheus installed without using
Prometheus Operator.
Therefore, support RabbitMQ alerting integration with and without using Prometheus Operator.
Auto-generate single Prometheus rule file from PrometheusRules.
Add Prometheus RabbitMQ scrape targets (do not rely on outdated
annotation approach).
* Remove line to set dev image since v1.7.0 will be cut very soon
* Make clear that Prometheus CRDs can be put in any namespace
...NamespaceSelector {} means any namespace will be selected.
This is not to be confused with value `nil` which means "only check own
namespace".
* Skip SSL verification in dev setup
Copy file name to clipboardExpand all lines: observability/README.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,8 @@
1
1
# Observability
2
2
3
-
This directory contains scrape targets, RabbitMQ alerting rules, Alertmanager configuration, and RabbitMQ dashboards published in a format that is compatible with [Prometheus Operator](https://github.com/prometheus-operator/prometheus-operator).
3
+
This directory contains scrape targets, RabbitMQ alerting rules, Alertmanager configuration, and RabbitMQ dashboards.
4
+
5
+
## Quick Start
4
6
5
7
If you don't have Prometheus and Grafana installed, the quickest way to try out RabbitMQ observability is as follows:
6
8
@@ -25,3 +27,4 @@ Learn more on RabbitMQ monitoring in:
RabbitMQ alerting rules depend on [kube-state-metrics](https://github.com/kubernetes/kube-state-metrics). Refer to the kube-state-metrics documentation to deploy and scrape kube-state-metrics.
4
+
5
+
## With Prometheus Operator
6
+
If Prometheus and Alertmanager are installed by [Prometheus Operator](https://github.com/prometheus-operator/prometheus-operator), apply the YAML files in [alertmanager](./alertmanager), [monitors](./monitors), and [rules](./rules) directories. They contain K8s objects watched by Prometheus Operator configuring Prometheus.
7
+
8
+
## Without Prometheus Operator
9
+
If Prometheus and Alertmanager are not installed by Prometheus Operator, use [config-file.yml](./config-file.yml) and [rule-file.yml](./rule-file.yml) as a starting point for RabbitMQ monitoring and alerting.
10
+
`rule-file.yml` is an auto-generated file containing the same rules as the [rules](./rules/) directory.
11
+
12
+
For the [Alertmanager configuration file](https://prometheus.io/docs/alerting/latest/configuration/#configuration-file), use the same `alertmanager.yaml` as provided in [alertmanager/slack.yml](alertmanager/slack.yml).
0 commit comments