KubeMQ's Notification features allows to subscribe to predefined events channel and receive real-time events for any access to KubeMQ resources.
This feature is useful for external auditing of access control attempts.
KubeMQ administrator can configure an Event channel which will be able to subscribe and receive access log notifications.
Access Notification Record consist from the following fields:
A unique notification id for the event
The message id which triggered the access attempt
The client id which tried to access the resource
The resource type: Events, Events Store, Queues, Commands, and Queries
The requested channel
The Action type: Send, Receive, Stream, Ack
The sub action type: Connect
The result of the request
Unix time of access attempt
Unix time of access result
A Notification event will be sent to an Event channel with the format of
Report-Channel-Prefix configuration of
Since Events message pattern support wildcards subscriptions, we have great flexibility to which channel we would like to monitor.
All notification channels
All notification events channels
All notification in any message pattern with channel name start with foo
All notification in any message pattern with channel name foo.bar only
KubeMQ allows to configure two settings:
1. Report Channel Prefix - allows to set the prefix report channel name
2. Log - Allows to log the notification to console stdout