Skip to content
This repository was archived by the owner on Nov 16, 2020. It is now read-only.

Option to disable metrics collector on startup #78

Merged
merged 2 commits into from
Apr 17, 2019

Conversation

dcorbacho
Copy link
Contributor

Allows external stats to be gathered for the prometheus plugin, while
removing all metrics collection/aggregation and unnecesary management
services.

To disable set app env disable_metrics_collector to true.
Defaults false

[#164376052]

Allows external stats to be gathered for the prometheus plugin, while
removing all metrics collection/aggregation and unnecesary management
services.

To disable set app env `disable_metrics_collector` to `true`.
Defaults `false`

[#164376052]
Copy link
Contributor

@gerhard gerhard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given the following rabbitmq.conf

management_agent.disable_metrics_collector = true

Only rabbit_mgmt_external_stats will be started:

image

This is what the process tree looks like without the above config setting:

image

The metrics made available by rabbitmq_prometheus are the same in both cases.

@gerhard gerhard merged commit cb0f55b into master Apr 17, 2019
@gerhard gerhard deleted the disable-metrics-collection branch April 17, 2019 11:44
gerhard added a commit to rabbitmq/rabbitmq-prometheus that referenced this pull request Apr 22, 2019
This has support for disabling metrics_collector, as captured in
rabbitmq/rabbitmq-management-agent#78 & rabbitmq/rabbitmq-management#691

Since we want management to be enabled, this doesn't help our use-case,
but this option is perfect for users that want metrics, but don't want
to pay the overhead of Management - especially metric aggregations.

[#164376052]
@gerhard gerhard restored the disable-metrics-collection branch April 22, 2019 21:04
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants