Hi Leonardo, try running a search "in the future", i. e. use an absolute time range and select a time in the future (more than 2 hours) as end of the time range.
If you see your messages, it's a simple problem with the timezones of the message timestamps (i. e. it's probably missing from the syslog messages and Graylog assumes it to be in UTC). Cheers, Jochen On Thursday, 5 January 2017 15:29:22 UTC+1, Leonardo D'Angelo Gonçalves wrote: > > Hi > > I've installed Graylog (2.1.2) with linux clients (syslog) with 2 > differents timezones (UTC and BRT), I noticed servers with UTC takes 2 > hours (timezone BRT is -02:00 from UTC) to display messages on graylog > console > > Anyone has this issue? > > User *admin*:2017-01-05 12:26:48 -02:00Your web browser:2017-01-05 > 12:26:48 -02:00Graylog server:2017-01-05 12:26:48 -02:00 > > > Graylog 2.1.2 > RHEL: 7.3 > Elasticsearch 2.4.3 > > -- 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/35f88749-18a2-4a3b-aa21-9e40980dc7ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
