Hi, the value of the timestamp field in the actual GELF message (1453388845999.000) is invalid or rather translates to a date very far in the future (48026-01-22T03:53:19.000Z to be exact).
The timestamp field in a GELF message has to contain the seconds (!) since UNIX epoch, not milliseconds since UNIX epoch; see https://www.graylog.org/resources/gelf/. I think it's simply a matter of an incorrect conversion in the library being used (1453388845.999 would translate to 2016-01-21T15:07:25.999Z which looks much more sane). Cheers, Jochen On Thursday, 28 January 2016 12:46:30 UTC+1, Skip Cole 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=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 > -- 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/b1b7bd24-fd0e-48cc-b1f9-aa65135d518c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
