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
Showing
+620 -20
.github/workflows/prometheus-rules.yml
0 → 100644
... | @@ -10,6 +10,7 @@ require ( | ... | @@ -10,6 +10,7 @@ require ( |
github.com/go-logr/logr v0.3.0 | github.com/go-logr/logr v0.3.0 | ||
github.com/go-stomp/stomp v2.1.4+incompatible | github.com/go-stomp/stomp v2.1.4+incompatible | ||
github.com/michaelklishin/rabbit-hole/v2 v2.8.0 | github.com/michaelklishin/rabbit-hole/v2 v2.8.0 | ||
github.com/mikefarah/yq/v4 v4.7.1 | |||
github.com/onsi/ginkgo v1.16.2 | github.com/onsi/ginkgo v1.16.2 | ||
github.com/onsi/gomega v1.11.0 | github.com/onsi/gomega v1.11.0 | ||
github.com/rabbitmq/rabbitmq-stream-go-client v0.0.0-20210422170636-520637be5dde | github.com/rabbitmq/rabbitmq-stream-go-client v0.0.0-20210422170636-520637be5dde | ||
... | ... |
observability/prometheus/README.md
0 → 100644
observability/prometheus/config-file.yml
0 → 100644
observability/prometheus/rule-file.yml
0 → 100644
Please register or sign in to comment