- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Development Guide
- Practical Tutorial
- API Documentation
- SDK Documentation
- FAQs
- General References
- Service Level Agreement
- Contact Us
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Development Guide
- Practical Tutorial
- API Documentation
- SDK Documentation
- FAQs
- General References
- Service Level Agreement
- Contact Us
The Plugin Management module allows you to view and manage plugins supported by a TDMQ for RabbitMQ cluster.
This document describes how to view supported plugins in the TDMQ for RabbitMQ console.
Viewing Plug-ins
1. Log in to the RabbitMQ console.
2. In the left sidebar, select Cluster, select an appropriate region, and click the ID of the target cluster to enter the cluster detail page.
3. At the top of the cluster detail page, select the Plugin Management tab to enter the plugin management page.
The following table describes plugins that are enabled by default after a TDMQ for RabbitMQ cluster is created.
Plugin | Description |
rabbitmq_event_exchange | The rabbitmq_event_exchange plugin can publish various events about the RabbitMQ server, such as connection creation and closure, channel creation and closure, and queue creation and deletion. These events are sent to a special exchange named amq.rabbitmq.event using messages. |
rabbitmq_management | The rabbitmq_management plugin provides web user interfaces and a set of HTTP APIs for managing and monitoring the RabbitMQ server. |
rabbitmq_peer_discovery_k8s | The rabbitmq_peer_discovery_k8s plugin allows RabbitMQ nodes to automatically discover and connect to other RabbitMQ nodes in a Kubernetes environment to form a cluster. |
rabbitmq_prometheus | The rabbitmq_prometheus plugin is a monitoring plugin provided by RabbitMQ. It can export RabbitMQ metrics in a format understandable by Prometheus. Therefore, you can use tools, such as Prometheus and Grafana to monitor and visualize the RabbitMQ performance and health status. |
rabbitmq_tracing | The rabbitmq_tracing plugin can trace messages passing through RabbitMQ and persist them to a disk or record them in log files, thereby reducing time in problem identification and debugging. |
Note:
TDMQ for RabbitMQ has the rabbitmq_delayed_message_exchange delayed message plugin Disabled by Default , due to the following risks and limitations of the plugin:
1. The current plugin's design is not suitable for scenarios with a high volume of delayed messages (unscheduled messages reaching hundreds of thousands or even millions). Please carefully evaluate the message throughput in a production environment to avoid unexpected long delay, message loss, and other issues.
2. Delayed messages only have one persistent copy on each node. If a node cannot function properly (for example, heaped messages cause continuous OOM leading to restarts and inability to recover), the delayed messages on that node cannot be consumed by the consumer side.
3. The delayed switch does not support setting mandatory . Producers cannot be notified about messages that could not be routed through basic.return events. Thus, before they send delayed messages, it is crucial to ensure that the corresponding switches, queues, and routing relationships exist.
For the original text on risks and limitations, please see the Official Usage Restriction Statement of the RabbitMQ Delayed Message Plugin.
Additionally, you can see the documentation TDMQ for RabbitMQ > Development Guide > Delayed Messages for two implementations of delayed messages described therein.
Yes
No
Was this page helpful?