There are several reasons why your organisation might want a log of all actions performed on an a9s Messaging instance:
- verifying that your apps are behaving as they should
- reviewing what went wrong after an incident
- checking that only apps/users you know about are connecting to a9s Messaging
For theses reasons we have an audit log feature for a9s Messaging that takes internal events from RabbitMQ (e.g.
binding.created, ...) and delivers them as Syslog (rfc5424) over TCP to an endpoint of your choice (maybe an a9s LogMe instance).
This feature has been developed for a9s RabbitMQ 3.7 and a9s Messaging 3.8 only, and therefore when enabled globally (all instances created by a service broker) RabbitMQ 3.6 should be disabled.
rabbitmq.audit_log.endpoint: should be the URL of Syslog endpoint where you would like to stream the logs of all of your RabbitMQ instances to e.g.
Enabling audit log support globally is simple, just include the
ops/rabbitmq-globaly-enable-audit-log.yml ops file with your deployment of