Manage Plugins

Last updated: 2025-08-11 11:25:07

Manage Plugins

Last updated: 2025-08-11 11:25:07

The main function of RabbitMQ plugins is to expand core features. By installing plugins, you can enhance the ability of Message Queue to meet specific business requirements. TDMQ for RabbitMQ provides a uniform way to view and manage supported plugins on the console.
Constraints and Limitations
TDMQ for RabbitMQ Serverless cluster does not support plugin management features.
Plugin Introduction
Plugin Name
Enabling Methods
Plugin Description
Usage Limits and Risk Description
rabbitmq_delayed_message_exchange
off by default
manually enable
The rabbitmq_delayed_message_exchange plug-in allows you to implement delayed message delivery in RabbitMQ. This means you can send a message to a special exchange and designate a delay time, after which the message will be sent to the appropriate queue.
1. The plug-in design is not suitable for scenarios with a high volume of delayed messages (unallocated messages reaching hundreds of thousands or even million entries). In a live production environment, cautiously evaluate the message scale to avoid unexpected long delays, message loss, and other issues.
2. Delayed messages have only one persistent replica on each node. If a node fails to run normally (for example, due to continuous OOM caused by message backlog and cannot be restored after restart), the delayed messages on that node cannot be consumed.
3. The Latency Switch does not support setting mandatory. Producers cannot use the basic.return event to detect messages that could not be routed. Therefore, ensure the corresponding switch, queue, and Routing Relationship exist before sending delayed messages.
For risks and limitations, see the official usage restrictions of the RabbitMQ Delayed Message Plugin. To use delayed messages, refer to the two methods introduced in Delayed Messages.
rabbitmq_event_exchange
enabled by default
cannot be turned off
The rabbitmq_event_exchange plug-in 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 as messages to the special exchange named amq.rabbitmq.event.
-
rabbitmq_management
enabled by default
cannot be turned off
The RabbitMQ_management plug-in provides a Web-based user interface and a group of HTTP APIs for rabbitmq server management and monitoring.
-
rabbitmq_peer_discovery_k8s
enabled by default
cannot be turned off
The rabbitmq_peer_discovery_k8s plug-in allows RabbitMQ nodes to auto discover and connect to other RabbitMQ nodes in Kubernetes environment, thereby forming a cluster.
-
rabbitmq_prometheus
enabled by default
cannot be turned off
The rabbitmq_prometheus plug-in is a monitoring plugin provided by RabbitMQ. It can export RabbitMQ metrics in Prometheus supported formats, enabling the use of tools like Prometheus and Grafana to monitor and visualize RabbitMQ performance and health status.
-
rabbitmq_tracing
enabled by default
cannot be turned off
The rabbitmq_tracing plug-in can track messages transiting RabbitMQ, persist them to disk, and record them in log files, thereby saving time cost for problem localization and debugging.
-
rabbitmq_shovel
Activation in the console is not supported.
The rabbitmq_shovel plug-in is for one-way message migration within the same cluster. It uses client connections at the underlying layer to transmit data. The message source and message target can be located in the same cluster or different clusters.
If activation is required, read the notes below carefully and submit a ticket to contact technical personnel for enabling the plug-in in the backend after confirmation.
1. This plug-in can be used for testing and business migration. It is not recommended for business production environment. Cluster stability issues caused by using this plug-in are not within the SLA scope guaranteed by Tencent Distributed Message Queue (TDMQ) RabbitMQ Edition.
2. Clusters under the same account (uin) in the same region have mutual network connectivity. If the clusters are in different regions, you need to establish network connectivity through Cloud Connect Network (CCN) before using the rabbitmq_shovel plug-in to migrate messages.
Viewing Plugins
1. Log in to the TDMQ RabbitMQ Console.
2. Select Cluster Management > Cluster List in the left sidebar, select region, click the Instance ID to view, and open the cluster details page.
3. On the cluster details page top, select the Plugin Manager tab to enter the plugin management page and view the all plugin list.
﻿
﻿

Was this page helpful?

You can also Contact Sales or Submit a Ticket for help.

Yes

Feedback

Plugin Name	Enabling Methods	Plugin Description	Usage Limits and Risk Description
rabbitmq_delayed_message_exchange	off by default manually enable	The rabbitmq_delayed_message_exchange plug-in allows you to implement delayed message delivery in RabbitMQ. This means you can send a message to a special exchange and designate a delay time, after which the message will be sent to the appropriate queue.	1. The plug-in design is not suitable for scenarios with a high volume of delayed messages (unallocated messages reaching hundreds of thousands or even million entries). In a live production environment, cautiously evaluate the message scale to avoid unexpected long delays, message loss, and other issues. 2. Delayed messages have only one persistent replica on each node. If a node fails to run normally (for example, due to continuous OOM caused by message backlog and cannot be restored after restart), the delayed messages on that node cannot be consumed. 3. The Latency Switch does not support setting mandatory. Producers cannot use the basic.return event to detect messages that could not be routed. Therefore, ensure the corresponding switch, queue, and Routing Relationship exist before sending delayed messages. For risks and limitations, see the official usage restrictions of the RabbitMQ Delayed Message Plugin. To use delayed messages, refer to the two methods introduced in Delayed Messages.
rabbitmq_event_exchange	enabled by default cannot be turned off	The rabbitmq_event_exchange plug-in 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 as messages to the special exchange named amq.rabbitmq.event.	-
rabbitmq_management	enabled by default cannot be turned off	The RabbitMQ_management plug-in provides a Web-based user interface and a group of HTTP APIs for rabbitmq server management and monitoring.	-
rabbitmq_peer_discovery_k8s	enabled by default cannot be turned off	The rabbitmq_peer_discovery_k8s plug-in allows RabbitMQ nodes to auto discover and connect to other RabbitMQ nodes in Kubernetes environment, thereby forming a cluster.	-
rabbitmq_prometheus	enabled by default cannot be turned off	The rabbitmq_prometheus plug-in is a monitoring plugin provided by RabbitMQ. It can export RabbitMQ metrics in Prometheus supported formats, enabling the use of tools like Prometheus and Grafana to monitor and visualize RabbitMQ performance and health status.	-
rabbitmq_tracing	enabled by default cannot be turned off	The rabbitmq_tracing plug-in can track messages transiting RabbitMQ, persist them to disk, and record them in log files, thereby saving time cost for problem localization and debugging.	-
rabbitmq_shovel	Activation in the console is not supported.	The rabbitmq_shovel plug-in is for one-way message migration within the same cluster. It uses client connections at the underlying layer to transmit data. The message source and message target can be located in the same cluster or different clusters.	If activation is required, read the notes below carefully and submit a ticket to contact technical personnel for enabling the plug-in in the backend after confirmation. 1. This plug-in can be used for testing and business migration. It is not recommended for business production environment. Cluster stability issues caused by using this plug-in are not within the SLA scope guaranteed by Tencent Distributed Message Queue (TDMQ) RabbitMQ Edition. 2. Clusters under the same account (uin) in the same region have mutual network connectivity. If the clusters are in different regions, you need to establish network connectivity through Cloud Connect Network (CCN) before using the rabbitmq_shovel plug-in to migrate messages.

tencent cloud

Constraints and Limitations

Plugin Introduction

Viewing Plugins