Opsview 6.8.x End of Support
With the release of Opsview 6.11.0 on February 2025, versions 6.8.x have reached their End of Support (EOS) status, according to our Support policy. This means that versions 6.8.x will no longer receive code fixes or security updates.
The documentation for version 6.8.9 and earlier versions will remain accessible for the time being, but it will no longer be updated or receive backports. We strongly recommend upgrading to the latest version of Opsview to ensure continued support and access to the latest features and security enhancements.
Message Queue
Opsview uses messages for all communication between all micro-services, this is based on RabbitMQ. The component is installed into /opt/opsview/messagequeue.
You can see what queues are set up and in use on the current server by using the following command (each Opsview Monitor server has its own message queue).
sudo -iu opsview /opt/opsview/messagequeue/sbin/rabbitmqctl list_queues
Commonly a collector is clustered with other collectors (always in an odd number, as per rabbitmqs recommendation). To view this information you may run the below.
sudo -iu opsview /opt/opsview/messagequeue/sbin/rabbitmqctl cluster_status
There is also a UI available for RabbitMQ, but you need to use an SSH tunnel to access it
ssh -L 15672:localhost:15672 orchestrator.mydomain.com
You can then use http://localhost:15672 to access the UI and log in using the opsview user credentials stored within the deploy configuration on the Orchestrator.