diff options
| author | Michael Klishin <klishinm@vmware.com> | 2021-08-17 22:16:30 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-08-17 22:16:30 +0300 |
| commit | ea75297bf875e43c733dc414d535584f54a533af (patch) | |
| tree | 48791cebce99650a3a5565319c423fb6fc223b47 /release-notes/3.9.4.md | |
| parent | 645a076742a2340cfe931804eb7c2a21c728b515 (diff) | |
| parent | 1ea83beadd1bee272e7bc9509da05187e32a6e8b (diff) | |
| download | rabbitmq-server-git-ea75297bf875e43c733dc414d535584f54a533af.tar.gz | |
Merge pull request #3312 from rabbitmq/alarms-metric1
Expose alarms as Prometheus metrics
Diffstat (limited to 'release-notes/3.9.4.md')
| -rw-r--r-- | release-notes/3.9.4.md | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/release-notes/3.9.4.md b/release-notes/3.9.4.md index a1ddcbe05d..51a0d3bc64 100644 --- a/release-notes/3.9.4.md +++ b/release-notes/3.9.4.md @@ -15,6 +15,15 @@ consistent release schedule. #### Enhancements + * New Prometheus metrics for alarms: + * `rabbitmq_alarms_file_descriptor_limit` 1|0 + * `rabbitmq_alarms_free_disk_space_watermark` 1|0 + * `rabbitmq_alarms_memory_used_watermark` 1|0 + + While some of the alarms have cluster-wide effect, these metrics are node-local. + + GitHub issue: [#2653](https://github.com/rabbitmq/rabbitmq-server/pull/2653) + * Nodes will now use four more environment variables, if set: `RABBITMQ_DEFAULT_USER` (overrides `default_user` in `rabbitmq.conf`), `RABBITMQ_DEFAULT_PASS` (overrides `default_pass`), `RABBITMQ_DEFAULT_VHOST` (overrides `default_vhost`) and `RABBITMQ_ERLANG_COOKIE` (sets [shared authentication secret value](https://www.rabbitmq.com/clustering.html#erlang-cookie)). These variables **are not recommended to be used in production** but can be the only realistic option in some environment, such as service containers, ECS, and so on. Most users should continue using `rabbitmq.conf` and a securely generated local cookie file. |