You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment it is recommended to install one exporter per rabbitmq without any loadbalancer in between.
Another option would be to run a loadbalancer between the exporter and the rabbitmq cluster.
one exporter -> loadbalancer -> rabbitmq cluster
The second option is currently not supported but normally used for installations in k8s. As a result the graphs in prometheus will have gaps (see #131 ). These gaps are caused by the self label which is added to nodes, exchanges, etc..
So it would be quite useful to add configuration option to prevent adding this label from all metrics:
RABBITMQ_CONNECTION with to options: direct (default) or loadbalancer
direct: self label is added to the metrics ( as now)
loadbalancer: self label is removed from all metrics
The text was updated successfully, but these errors were encountered:
At the moment it is recommended to install one exporter per rabbitmq without any loadbalancer in between.
Another option would be to run a loadbalancer between the exporter and the rabbitmq cluster.
one exporter -> loadbalancer -> rabbitmq cluster
The second option is currently not supported but normally used for installations in k8s. As a result the graphs in prometheus will have gaps (see #131 ). These gaps are caused by the self label which is added to nodes, exchanges, etc..
So it would be quite useful to add configuration option to prevent adding this label from all metrics:
RABBITMQ_CONNECTION
with to options:direct
(default) orloadbalancer
direct
: self label is added to the metrics ( as now)loadbalancer
: self label is removed from all metricsThe text was updated successfully, but these errors were encountered: