EventSubscription and EventNotification

The EventSubscription interface is the client configuration piece. You use that to setup event notifications subscriptions and tell the BIG-IP where to send EventNotification messages to. The EventNotification interface is the outbound interface that the BIG-IP uses to send notifications back to your listener (which may or may not be the same client you used to configure the subscriptions). Your listener needs to have an HTTP endpoint that implements the EventNotification interface.

The flow goes something like this

1. Client code using EventSubscription methods calls the BIG-IP to configure which events to listen on and the URL where the BIG-IP sends the notification messages to.
2. Event occurs on BIG-IP and message is sent to EventNotification listener configured in 1.
3. If connection fails on 5 attempts to the EventNotification URL, then the subscription is put in a "disabled" state and must be re-enabled with the client EventSubscription methods.
4. Client uses EventSubscription methods to query the status and statistics of the subscription.

Here's an article I wrote a long time ago about how the pieces work

https://devcentral.f5.com/articles/the-new-icontrol-event-api

It seems some of the embedded images are missing but the content should get you where you are going.

A while back I also wrote 3 codeshare samples that illustrate the various pieces written in Perl.

• EventSubscription Client
• EventNotification Listener
• EventNotification Client (for testing your listener implementation

Hope this helps...

-Joe