Hello, We have a problem with the @timestamp field. Sometimes it is wrongly created as string instead of date.
We use the following pipeline: Docker -- mixed logs in GELF format --> graylog2-server1 -- only JSON logs in GELF format --> graylog2-server2. Both graylog2 servers are connected to the same ElasticSearch cluster. Each graylog2-server uses a separate index-pattern. Graylog2 version is 1.3.4. The indexes of graylog2-server2 should always create the @timestamp field as date. Is there a way to force graylog2 to use always date? Thanx in advancd! -- 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/8d28b51f-ef1f-4da7-85fc-9844a5ca5903%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
