Invalid timestamp about gelfj HOT 11 CLOSED

@todvora Thanks for PR. Merged and released as v1.1.16. Should be available in Central shortly.

Edit: mistyped released version

from gelfj.

This came up in a bug report for Graylog 2.3.0-rc.2: Graylog2/graylog2-server#4027

The "timestamp" field should definitely be a floating point number and not a string.

from gelfj.

+1

any ETA on this ? It is hurting my app and we are dropping a lots of messages.

Thanks

from gelfj.

@bonzi316 Graylog doesn't drop GELF messages in which the timestamp field is a string.

See the referenced Graylog2/graylog2-server#4027 for details.

from gelfj.

This no longer seems to be true for graylog 2.4.0 (messages are not appearing anymore).

from gelfj.

@tholu I am seeing the same behavior. My graylog logs are filling up with warnings calling out invalid timestamps. I had read they should be processed still, per @joschi, but I do not see gelfj messages indexed in graylog at all. Looks like @todvora may have a fix. Are you thinking of PRing that back here?

from gelfj.

@jasonvangundy This repo does not seem to be maintained anymore. You can use v1.1.16 from https://github.com/todvora/gelfj/releases via https://jitpack.io/ to fix it (already tested and in production).

from gelfj.

Thanks @tholu ! You must be getting a different result than I am. You aren't seeing the following? https://jitpack.io/com/github/todvora/gelfj/v1.1.16/build.log

from gelfj.

Sorry about that, @jasonvangundy - this is a failed and cached build. You can now get the v1.1.17, which builds fine: https://jitpack.io/#todvora/gelfj/v1.1.17

from gelfj.

Here is my PR with the mentioned fix: #121

from gelfj.

Awesome, thank you @t0xa!

from gelfj.