Users must be granted permissions for management UI access. Separate ports should be used by those clients. Note that the UI and HTTP API port - typically 15672 - does not support AMQP 0-9-1, AMQP 1.0, STOMP or MQTT connections. Or (provided that localhost resolves correctly). It can be accessed by users with sufficient privileges at either The management UI can be accessed using a Web browser at :15672/.įor example, for a node running on a machine with the hostname of warp10.local, Node restart is not required after plugin activation.ĭuring automated deployments, the plugin can be enabled viaĮnabled plugin file. Rabbitmq-plugins enable rabbitmq_management Like any other plugin, it mustīe enabled before it can be used. The management plugin is included in the RabbitMQĭistribution. It is recommended for production environments. RabbitMQ provides first class support for Prometheus and Grafana as of 3.8. Collection and aggregation of node-specific metrics which is more resilient to individual node failures.Metric access permissions are not specific to RabbitMQ.Ease of metric data sharing: both metric state and dashboards.More powerful and customizable user interface.Access to additional related metrics such as those of the Erlang runtime ones.Decoupling of the monitoring system from the system being monitored.Or the ELK stack are more suitable options for production systems. Long term metric storage and visualisation services such as Prometheus and Grafana Management UI access is controlled via the RabbitMQ permission tags system.
0 Comments
Leave a Reply. |