Add node metrics provided by management API #55
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some users (see #37 and #13) requested node metrics such as file descriptors, sockets, memory and disk alarms to be available in Prometheus.
All these are accessible through
rabbit_mgmt_db:augment_nodes
, and this PR allows them to be displayed as part ofprometheus_rabbitmq_nodes_collector
data. Detailed node stats are disabled by default, and can be configured tolocal
orall
.local
will provide the detailed stats from the node that is being queried andall
for the whole cluster. The last setting is only recommended if metrics are being pulled from a single node. When all nodes in the cluster are configured as prometheus targets,local
should be used.Memory and disk alarms can be configured in prometheus as
rules
, such as:mem_alarm
anddisk_free_alarm
can be used instead, which display a boolean indicating whether an alarm is active in the cluster.This PR might also reduce the need for
prometheus_process_collector
for monitoring, or provide an alternative in some situations, which can be problematic because of the inclusion of NIFS (see issue #12).Closes
37
and13
.Example of scrape: