root
/
rabbitmq-server
mirror of https://github.com/rabbitmq/rabbitmq-server.git
1
0
Fork 0
Code Issues Actions 2 Packages Projects Releases Wiki Activity
rabbitmq-server/deps/rabbitmq_prometheus/docker/rabbitmq-overview.conf

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

32 lines
1.1 KiB
Plaintext
Raw Permalink Normal View History

Finish Erlang Distribution Grafana dashboard Includes Erlang node to colour pinning Adds a few make targets to help with docker-compose repetitive commands & Grafana dashboard updates. Split Overview & Distribution Docker deployments re deadtrickster/prometheus.erl#92 [finishes #166004512]
2019-05-30 01:19:09 +08:00
# https://github.com/rabbitmq/rabbitmq-server/blob/master/docs/rabbitmq.conf.example
Capture a 3-node RabbitMQ & Prometheus + Grafana stack cd docker && docker-compose up [#164374321]
2019-04-16 02:18:45 +08:00
loopback_users.guest = false
listeners.tcp.default = 5672
management.listener.port = 15672
management.listener.ssl = false
Improve node naming, standardise the colour pinning regex
2019-06-18 05:20:54 +08:00
vm_memory_high_watermark.absolute = 768MiB
Set demo-friendly memory & disk-space limits Capture limits in thresholds. Even if they are static and somewhat specific to this RabbitMQ deployment, it's better to have them when demo-ing the end-to-end Prometheus/Grafana experience. [#164374751]
2019-04-24 01:56:30 +08:00
Set cluster name via config Now that there is a 3.8 alpha build that includes rabbitmq/rabbitmq-server#2075, let's make use of it! Without this, when a new cluster was started, some nodes ended up wtih `rabbit@localhost` for the cluster label, instead of e.g. `rmq-gcp-38`. The main suspect was a race condition, where the rabbitmq_prometheus app starts before the cluster name is set via `rabbitmqctl set_cluster_name`. [finishes #167835770]
2019-08-13 22:50:01 +08:00
cluster_name = rabbitmq-overview
Capture a 3-node RabbitMQ & Prometheus + Grafana stack cd docker && docker-compose up [#164374321]
2019-04-16 02:18:45 +08:00
cluster_formation.peer_discovery_backend = rabbit_peer_discovery_classic_config
Improve node naming, standardise the colour pinning regex
2019-06-18 05:20:54 +08:00
cluster_formation.classic_config.nodes.1 = rabbit@rmq0
cluster_formation.classic_config.nodes.2 = rabbit@rmq1
cluster_formation.classic_config.nodes.3 = rabbit@rmq2
Mirror slow-consumer-persistent queue to all 3 nodes This puts load on the distribution and makes the Erlang-Distribution dashboard show an interesting behaviour in TCP sockets. @dcorbacho thinks so too. re deadtrickster/prometheus.erl#92 [#166004512]
2019-05-16 01:49:58 +08:00
Filter Grafana dashboards by namespace (#2719) So that clusters with the same rabbitmq_cluster name in different K8s namespaces don't clash Namespace filter comes first, because the order of the layers is namespace -> cluster -> node Tested with the latest 3.9.0 dev build We had to account for plugin changes from .ez to directories & the management.load_definitions deprecation which would prevent a node from booting (fixed in https://github.com/rabbitmq/rabbitmq-server/commit/07a0dd743834b8cc76beec579c4b31845f8381f2). This commit didn't make it through the 3.9.x pipeline yet, so there is no 3.9.0 dev build with this fix yet. The simplest fix is to drop `management.` from the load_definitions config. The next manual step is to generate all dashboards using e.g. `make RabbitMQ-Overview.json > ~/Downloads/RabbitMQ-Overview.json` and upload them to https://grafana.com/orgs/rabbitmq Great contribution @ansd, thank you 👏🏻
2021-01-19 02:45:05 +08:00
load_definitions = /etc/rabbitmq/rabbitmq-definitions.json
Finish Erlang Distribution Grafana dashboard Includes Erlang node to colour pinning Adds a few make targets to help with docker-compose repetitive commands & Grafana dashboard updates. Split Overview & Distribution Docker deployments re deadtrickster/prometheus.erl#92 [finishes #166004512]
2019-05-30 01:19:09 +08:00
# background_gc_enabled = true
Increase Prometheus scrape to 15s & match across all metrics We want to use a consistent range for all metrics that use rate() and a safe value (4x the Prometheus scrape interval): https://www.robustperception.io/what-range-should-i-use-with-rate This also prompted a change in RabbitMQ's default collect_statistics_interval, so that we don't update metrics unnecessarily. We are OK if the Management UI doesn't update on every 5s auto-refresh. Related https://github.com/rabbitmq/rabbitmq-website/commit/a929f22233842fe8b2046d1bc870a6b2ef7a23dd [#167846096]
2019-08-14 00:20:49 +08:00
# Increase the 5s default so that we are below Prometheus' scrape interval,
# but still refresh in time for Prometheus scrape
# This is linked to Prometheus scrape interval & range used with rate()
collect_statistics_interval = 10000
Add option to disable stats in management to overview example Commented by default - we don't want to shock people just yet.
2019-09-27 00:35:06 +08:00
# Run RabbitMQ Management in Management-only mode, no stats
# https://github.com/rabbitmq/rabbitmq-management/pull/707
# management.disable_stats = true
Bump to latest RabbitMQ 3.9.0 dev build & Erlang/OTP v22.2.6 Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
2020-02-07 01:40:46 +08:00
Improve config for returning metrics per object Since metrics are now aggregated by default, it made more sense to use the inverse meaning of disabling aggregation, and call it a positive and explicit action: return_per_object_metrics. Naming pair: @michaelklishin Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
2020-02-11 21:08:00 +08:00
# Return per-object metrics (unaggregated)
Bump to latest RabbitMQ 3.9.0 dev build & Erlang/OTP v22.2.6 Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
2020-02-07 01:40:46 +08:00
# https://github.com/rabbitmq/rabbitmq-prometheus/pull/28
Improve config for returning metrics per object Since metrics are now aggregated by default, it made more sense to use the inverse meaning of disabling aggregation, and call it a positive and explicit action: return_per_object_metrics. Naming pair: @michaelklishin Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
2020-02-11 21:08:00 +08:00
# prometheus.return_per_object_metrics = true