RabbitMQ Support Policy
Support Policy
Matrix42 Software uses RabbitMQ as messaging middleware.
We ensure that our applications use RabbitMQ correctly in accordance with the documented interfaces and system requirements. However, responsibility for basic RabbitMQ functionality (e.g., troubleshooting the broker) lies primarily with the RabbitMQ provider itself (e.g., VMware Tanzu or the open-source community support).
Matrix42 is responsible for the following:
- Installation and configuration of RabbitMQ using the provided installation routine on a Windows system
- Functionality of Matrix42 software in conjunction with RabbitMQ
- Correct use of RabbitMQ APIs/protocolsUnterstützte RabbitMQ-Versionen
- see FAQ section
- Configuration guidelines related to Matrix42 software (e.g., exchanges, queues, TTLs, rights)
- Troubleshooting in the context of Matrix42 applications (logs, message format, error messages)
Matrix42 is NOT responsible for the following:
- Operation of the RabbitMQ instance
- Installation, configuration, or operation of a RabbitMQ cluster
- Cluster setup, load balancing, HA strategies, network/firewall/TLS certificates
- Monitoring, maintenance, upgrades, scaling, high availability
- Performance optimization of the infrastructure
- Debugging third-party applications that also use RabbitMQ
- Security optimization of the RabbitMQ system
- Backup, restore, or failover concepts for the queue infrastructure
FAQ
Q: Which RabbitMQ versions are supported?
A: A list of supported versions can be found in our system requirements.
https://help.matrix42.com/010_SUEM/010_UUX_for_Secure_UEM/010_Installation_and_Configuration/030_Transport_Service/Service_Bus_I%3A_RabbitMQ/RabbitMQ_Release_Notes
Q: Why don't you fully support RabbitMQ?
A: RabbitMQ is a standalone infrastructure system, like a database or a Kubernetes cluster. We focus on Matrix42's own software — RabbitMQ operation is the responsibility of the customer.
Q: What happens in the event of performance problems?
A: We test the impact of our software. Cluster design or hardware bottlenecks are the responsibility of the customer.