RabbitMQ Resource

RabbitMQ is an open source messaging system used to facilitate communication and data sharing between distributed applications and components. It works as a message broker, allowing producers to send messages to queues and consumers to receive and process them. RabbitMQ offers a flexible architecture based on the AMQP (Advanced Message Queuing Protocol) standard, supporting various messaging models, such as message queuing, direct exchange, topic exchange and header exchange. It ensures reliable message delivery, handles queues, and supports horizontal scalability to handle intensive workloads. RabbitMQ is especially adopted in distributed environments, microservices, asynchronous processing systems, application integration and real-time notifications, providing a reliable and flexible solution for exchanging messages between components of a system.

How to monitor RabbitMQ on One Platform

1 – In the side menu, click on Services Hub



2 – In the Queue category, click on the RabbitMQ card



3 – You will be directed to the RabbitMQ configuration form, fill in the fields



4 – If you want, you can configure automatic incident opening. In the Open automatic incident section, fill in the fields:

  • Severity -> Choose between “SEV-1 – Critical”, “SEV-2 – High”, “SEV-3 – Moderate”, “SEV-4 – Low”, “SEV-5 – Informational” or “Not Classified”;
  • Check Interval in seconds -> This is the interval at which checking will take place (this interval cannot be less than the number of failures x the Interval configured in the monitoring form;
  • Failures to open automatic incident -> It is the number of failures necessary to open the automatic incident;
  • Check Interval in seconds -> This is the interval in which checking will take place (this interval cannot be less than the number of hits x the Interval configured in the monitoring form;
  • Hits to close automatic incident -> It is the number of hits needed to close the automatic incident;
  • Responders -> These are the teams that will be notified if there are incidents in this monitoring, and you can add one or multiple teams;

If necessary, you can create a team by clicking + RESPONDER, you will be directed to the form

to create the team, then click on the button  for the new team to appear in the list

***Don’t forget to activate the Enable to set up automatic incidents opening toggle to save the automatic incident opening settings



5 – Click on CREATE MONITORING 


RabbitMQ is an open source messaging system used to facilitate communication and data sharing between distributed applications and components. It works as a message broker, allowing producers to send messages to queues and consumers to receive and process them. RabbitMQ offers a flexible architecture based on the AMQP (Advanced Message Queuing Protocol) standard, supporting various messaging models, such as message queuing, direct exchange, topic exchange and header exchange. It ensures reliable message delivery, handles queues, and supports horizontal scalability to handle intensive workloads. RabbitMQ is especially adopted in distributed environments, microservices, asynchronous processing systems, application integration and real-time notifications, providing a reliable and flexible solution for exchanging messages between components of a system.

How to monitor RabbitMQ on One Platform

1 – In the side menu, click on Services Hub



2 – In the Queue category, click on the RabbitMQ card



3 – You will be directed to the RabbitMQ configuration form, fill in the fields



4 – If you want, you can configure automatic incident opening. In the Open automatic incident section, fill in the fields:

  • Severity -> Choose between “SEV-1 – Critical”, “SEV-2 – High”, “SEV-3 – Moderate”, “SEV-4 – Low”, “SEV-5 – Informational” or “Not Classified”;
  • Check Interval in seconds -> This is the interval at which checking will take place (this interval cannot be less than the number of failures x the Interval configured in the monitoring form;
  • Failures to open automatic incident -> It is the number of failures necessary to open the automatic incident;
  • Check Interval in seconds -> This is the interval in which checking will take place (this interval cannot be less than the number of hits x the Interval configured in the monitoring form;
  • Hits to close automatic incident -> It is the number of hits needed to close the automatic incident;
  • Responders -> These are the teams that will be notified if there are incidents in this monitoring, and you can add one or multiple teams;

If necessary, you can create a team by clicking + RESPONDER, you will be directed to the form

to create the team, then click on the button  for the new team to appear in the list

***Don’t forget to activate the Enable to set up automatic incidents opening toggle to save the automatic incident opening settings



5 – Click on CREATE MONITORING