Hi Jan,

Thanks for the reply. The thing is, we are passing in the timestamp. Here
is a 'toString' of the GelfMessage:

GelfMessage{version="1.1" timestamp="1453388845999.000"
short_message="{timestamp=2016-01-21T10:07:25.999-05:00, level=DEBUG,
action=HTTP_REQUEST, user=felixfrankfurter}", level="ALERT(1)"}

I notice that the timestamp in the short message is not in the right
format, so I'm going to change that, and see if that helps. But I thought
that the timestamp set at the higher level would be sufficient.

I'll try this change out, and let you know how it goes.

Thanks,
Skip

On Thu, Jan 28, 2016 at 6:44 AM, Skip Cole <[email protected]> wrote:

> Hi Jan,
>
> Thanks for the reply. The thing is, we are passing in the timestamp. Here
> is a 'toString' of the GelfMessage:
>
> GelfMessage{version="1.1" timestamp="1453388845999.000"
> short_message="{timestamp=2016-01-21T10:07:25.999-05:00, level=DEBUG,
> action=HTTP_REQUEST, user=hso_admin}", level="ALERT(1)"}
>
> I notice that the timestamp in the short message is not in the right
> format, so I'm going to change that, and see if that helps. But I thought
> that the timestamp set at the higher level would be sufficient.
>
> I'll try this change out, and let you know how it goes.
>
> Thanks,
> Skip
>
> On Thu, Jan 28, 2016 at 4:33 AM, Jan Doberstein <[email protected]> wrote:
>
>> Hej Skip,
>>
>> just an idea - based on that what you have written.
>>
>> If you change the timestamp in gelf, graylog is not able to parse this.
>> (Reference: https://www.graylog.org/resources/gelf/ )
>>
>> *timestamp* number
>>
>> Seconds since UNIX epoch with optional decimal places for milliseconds;
>> SHOULD be set by client library. Will be set to NOW by server if absent.
>>
>> I guess that this will explain your findings ...
>>
>> regards
>> Jan
>>
>> 2016-01-27 17:26 GMT+01:00 Skip Cole <[email protected]>:
>>
>>> Dear Wonderfull People,
>>>
>>> We send gelf messages to graylog to record our usage events. I have
>>> manipulated the gelf message to have the timestamp we want, but the
>>> messages are all showing up in graylog at the moment they were received. (I
>>> dump in 100 messages of events that took place over a 2 week period, and
>>> they all show up in the graphs at the moment I uploaded them.)
>>>
>>> I have been banging my head on this, and I bet there is a simple way
>>> around it. Any ideas?
>>>
>>> Thanks,
>>> Skip
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Graylog Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/graylog2/0f677733-078f-4ae1-82d2-423ee7d3b62d%40googlegroups.com
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> | Voice: +49 173 7100308 | Text: [email protected]
>> | http:// <http://about.me/jandoberstein>jalogis.ch/bio
>> |---
>> | send from my extraordinary device
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Graylog Users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/graylog2/o6inV7A4PBw/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/graylog2/CAGm-bLYnRSnAx1ZfRq_%2BJBztQZNrH8nLrEKeCQwbizFwUrwzHg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/graylog2/CAGm-bLYnRSnAx1ZfRq_%2BJBztQZNrH8nLrEKeCQwbizFwUrwzHg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/CAHYTHi6opighYqS2rCVukZ6DeAsmp-XpELkM%3Dihtpk3oU5fDuw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to