Event Sequence Documentation

Question

Is there any documentation that shows the sequence of when events fire?&nbsp;
&nbsp;Specifically, I am unsure of the relationship between HTTP_REQUEST and LB_SELECTED - which comes first, how do they interact, and how OneConnect effects them? &nbsp;
&nbsp;That said a good flow around most of the common event for HTTP and HTTPS would be appreciated.

brad_11480 · Answer

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. 
&nbsp;  
&nbsp; 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. 
&nbsp;  
&nbsp; 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. 
&nbsp;  
&nbsp; depending on the message different events may trigger, I assume, so showing these variants would be useful. 
&nbsp;  
&nbsp; Thanks so much to anyone (hey if someone is writing a book-- this would be a big seller!!!!). 
&nbsp;  
&nbsp;  
&nbsp;  &nbsp;

hoolio · Answer

Hi Brad, 
&nbsp;  
&nbsp; 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: 
&nbsp;  
&nbsp;  
&nbsp; http://devcentral.f5.com/Default.aspx?tabid=53&amp;view=topic&amp;postid=24619&amp;ptarget=24622 
&nbsp;  
&nbsp; 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 :  
&nbsp;  
&nbsp; Request events:  
&nbsp; ---------------------------------------------  
&nbsp; CLIENT_ACCEPTED - clientside - triggered when LTM receives and accepts a connection from a client  
&nbsp; HTTP_REQUEST - clientside - triggered when an HTTP profiles  
&nbsp; HTTP_REQUEST_DATA - clientside - triggered if HTTP::collect was called in HTTP_REQUEST  
&nbsp; LB_SELECTED - clientside - triggered when a node has been selected per the load balancing algorithm  
&nbsp; LB_FAILED - clientside - triggered when a node couldn't be selected or isn't reachable  
&nbsp; SERVER_CONNECTED - serverside - triggered when a connection is established with the node  
&nbsp; HTTP_REQUEST_SEND - serverside - triggered when LTM sends the HTTP request to the node  
&nbsp; CLIENT_CLOSED - clientside - triggered when the client connection is closed  
&nbsp;  
&nbsp; Response events:  
&nbsp; ---------------------------------------------  
&nbsp; HTTP_RESPONSE - serverside - triggered when LTM receives the HTTP response from the node  
&nbsp; HTTP_RESPONSE_DATA - serverside - triggered if HTTP::collect was called in HTTP_RESPONSE  
&nbsp; SERVER_CLOSED - serverside - triggered when the server connection is closed  
&nbsp; &nbsp; 
&nbsp;  
&nbsp; 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. 
&nbsp;  
&nbsp; If you have more specific questions, please elaborate. 
&nbsp;  
&nbsp; Thanks, 
&nbsp; Aaron

Forum Discussion

AppWorld Berlin iRules Contest!

F5 AppWorld 2026 Las Vegas - iRules Contest Winners!

Recent Discussions

VIP control across data centers - how to ensure only 1 VIP is up at a time?

FQDN Node Configuration

Logical Disk Full to Migrate rSeries

Priority Group Activation is not working

Changes to DO and AS3 GitHub - no longer monitored

Related Content

TCP Internals: 3-way Handshake and Sequence Numbers Explained

iRule Event Order Flowchart

Kia Telematics, Telecom Security, and Documentation.

iRules: Disabling Event Processing

iRule Event Order