Forum Discussion
jkstraw_44238
Apr 20, 2007Nimbostratus
Thank you for the tip - but unfortunately these are not unique numbers. I tailed the output after updating the iRule and found that the http::request_num was showing many duplicates for different unique requests.
I then looked up the HTTP::request_num and found it "returns the number of HTTP requests that a client made on the connection" so these numbers will never be unique. We avg 500,000 hits per day and pull a lot of stats from our existing apache logs. So need a solution that ties request and response metrics uniquely.
With our apache custom log a unique identifier isn't as important because both the request and response are on the same log line (apache doesn't even log until it gets the response or times out).
Since in this case each request/response pairing is logged separately it is an issue (the same is true of sendmail logs, there is a unique identifier which allows you to correlate the message as it transverses the mail subsystems).
Any other ideas?
Thanks again.