Event Sequence Documentation

Gosh, is that all there is about the events and their sequence and relationship to each other? All the link above provides is the list of events.

 

 

I too have been curious and it would be really helpful if there was a 'roadmap' of events and how they occur in the 'life of a message' going through the F5.

 

 

perhaps a tour that shows from the arrival of a message and what events trigger when as it passes through and also for the response as it passes through.

 

 

depending on the message different events may trigger, I assume, so showing these variants would be useful.

 

 

Thanks so much to anyone (hey if someone is writing a book-- this would be a big seller!!!!).

 

 

 

 

Hi Brad,

 

 

This type of info is sprinkled across various posts depending on which protocol you're working with. Here are the events I'd expect for a typical HTTP request and response:

 

 

 

http://devcentral.f5.com/Default.aspx?tabid=53&view=topic&postid=24619&ptarget=24622

 

 

Event code is triggered as the event occurs. The events are triggered based on profiles on the VIP. For a standard VIP with a TCP and HTTP profile, the following events could be triggered :

 

 

Request events:

 

---------------------------------------------

 

CLIENT_ACCEPTED - clientside - triggered when LTM receives and accepts a connection from a client

 

HTTP_REQUEST - clientside - triggered when an HTTP profiles

 

HTTP_REQUEST_DATA - clientside - triggered if HTTP::collect was called in HTTP_REQUEST

 

LB_SELECTED - clientside - triggered when a node has been selected per the load balancing algorithm

 

LB_FAILED - clientside - triggered when a node couldn't be selected or isn't reachable

 

SERVER_CONNECTED - serverside - triggered when a connection is established with the node

 

HTTP_REQUEST_SEND - serverside - triggered when LTM sends the HTTP request to the node

 

CLIENT_CLOSED - clientside - triggered when the client connection is closed

 

 

Response events:

 

---------------------------------------------

 

HTTP_RESPONSE - serverside - triggered when LTM receives the HTTP response from the node

 

HTTP_RESPONSE_DATA - serverside - triggered if HTTP::collect was called in HTTP_RESPONSE

 

SERVER_CLOSED - serverside - triggered when the server connection is closed

 

 

 

 

What protocol are you working with? You could figure out which events are triggered by creating a rule, adding it to the VIP, add all of the events with log statements, try to save the rule and then remove the ones that aren't valid based on the profiles you're using.

 

 

If you have more specific questions, please elaborate.

 

 

Thanks,

 

Aaron