unique request ids

[Mit Rowe]

for our purposes, it would have to be done at the point of log writing
(primarily, but not limited to, the need to ensure that if for whatever
reason we have to re-process a log file that we can quickly identify lines
already written to the db via a unique index).



On Wed, Nov 2, 2011 at 3:54 PM, AD <straightflush at gmail.com> wrote:

> we do something similar.  My suggestion,
>
>  md5(logentry + currentTimeInMilliseconds) as your key as you loop through
> the logfile
>
>
>
> On Wed, Nov 2, 2011 at 3:03 PM, Mit Rowe <mit at stagename.com> wrote:
>
>> Hello!
>>
>> For many reasons (QA, performance analytics, etc) we log all of our proxy
>> traffic into a database.
>>
>> We do this with varnish by collecting a text log via varnishncsa -F and a
>> CSV formatted string, and regularly run a batch process that inserts this
>> CSV data into a database.
>>
>> I was wondering... does varnish internally generate a reliably random
>> unique value for each request (similar to mod_unique_id in apache or a
>> uuid/guid), and if so is there a way that i can write it out to my logs,
>> perhaps via an insertion into a request header and using the %{HEADER}i
>> macro in varnishncsa?
>>
>> -Mit
>>
>>
>>
>> _______________________________________________
>> varnish-misc mailing list
>> varnish-misc at varnish-cache.org
>> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>>
>
>


-- 
Will 'Mit' Rowe
Stagename*
*1-866-326-3098
mit at stagename.com <josh at stagename.com>
www.stagename.com
Twitter: @stagename

*The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of this
information by persons or entities other than the intended recipient is
prohibited. If you received this transmission in error, please contact the
sender and delete all material contained herein from your computer.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20111102/7ea99a1e/attachment-0003.html>