> I was wondering if a GUID filter would be nice. It would generate a GUID for
> each event so it would be pretty easy to find a single event in the mass.

> Is this overkill? Is there an easy or already implemented way of doing this?

> Regards!

> Actually I think a GUID or some sort of ID generator WOULD be a good
> idea for the use case you described. I wonder if we could even use an
> event.sprintf on it so that you could add a new field with the full
> URL to the event embedded. Interesting.

> On Mon, Aug 6, 2012 at 5:09 PM, Jan Seidl <li...@heavyworks.net> wrote:
>> I see.

>> I was wondering in having a guid/uuid not being dependent on the event
>> content. More as working as an internal identification number.

>> It would be nice to add to ticketing systems something like "as stated by
>> evidences on log event ' 21f7f8de-8051-5b89-8680-0195ef798b6a' ...".

>> On 08/06/2012 05:54 PM, John Vincent wrote:

>> I took a stab at an experimental checksum filter* Note that
>> ElasticSearch I though assigned a unique id to an event it stores.

>> * https://gist.github.com/2857059

>> On Mon, Aug 6, 2012 at 3:56 PM, Jan Seidl <li...@heavyworks.net> wrote:

>> Hi Folks,

>> I was wondering if a GUID filter would be nice. It would generate a GUID for
>> each event so it would be pretty easy to find a single event in the mass.

>> Is this overkill? Is there an easy or already implemented way of doing this?

>> Regards!