Log unique Client Addresses per (Hour|Day|Etc)

I originally started to do that with the LDAP work I did in the iRUle referenced above. Unfortunately it doesn't scale very well, and isn't very reliable.

 

 

Using UDP, is fire & forget. If the receiver can't keep up, you lose messages (This was bad for me. May be OK for your requirements though).

 

 

Using TCP is a stream of data (No loss). But the buffers are tiny. When they fill up (i.e. receiver can't keep up), the LTM opens a NEW connection to the logging pool... Then when the pool is busy and can't keep up, you get an endless spiral where the number of HSL connections quickly brings everything to it's knees (I had it up to thousands of connections :). WHich rapidly gets messy as it can take a LONG time to process all those streams. WHich uses up all that memory you're trying to avoid in not using the tables in the first place.

 

 

Oh... HSL also delivers messages out of order... With both UDP and TCP. Again, your requirements may not care, but mine did when trying to perform stats calculations from individual messages.

 

 

At least with tables you can remain in control... (e.g. Flush when necessary to free up memory etc, as well as keeping HSL within useful bounds). Whereas with HSL you have none.

 

 

H