Logs delayed on time

[phil95 (phil)]

Hello everyone,
I have a very strange behavior of graylog, i’m located in Paris

Current default time zone: ‘Europe/Paris’
Local time is now: Tue Apr 9 15:29:15 CEST 2019.
Universal Time is now: Tue Apr 9 13:29:15 UTC 2019.

the logs create now appear in Graylog 2h after…
How can i fix that ?

If i understand well the messages are considered like being in UTC time ?
but how can i change that from graylog ?

Thanks in advance

[tmacgbay]

What is the time zone on the sending device?

[phil95 (phil)]

It’s also Paris time

[jan (Jan Doberstein)]

does the logfile contain a timestamp information?

If not Graylog assume that the ingested time is UTC … .

[phil95 (phil)]

Yeah the log file doesnt not contains timestamp info

date=2019-04-09 time=14:32:11 devname=4f-net-B devid=7008965 logid=0000000013 type=traffic subtype=forward level=notice vd=interne srcip=192.168.10.26 srcport=51460 srcintf=“interco-fw-int” dstip=10.4.33.25 dstport=8443 dstintf=“interco-infra” poluuid=a-c7cc24e7ecd1 sessionid=481086 proto=6 action=close policyid=278 policytype=policy dstcountry=“Reserved” srccountry=“Reserved” trandisp=noop service=“SVC-TCP-8443” duration=10 sentbyte=525 rcvdbyte=132 sentpkt=6 rcvdpkt=3 appcat=“unscanned” devtype=“Fortinet Device” mastersrcmac=00:09:0f:09:27:04 srcmac=00:09:0f:09:27:04

Is it possible simply with the extractors to add 2h on the UTC timestamp create by graylog ?

[jan (Jan Doberstein)]

with the processing pipelines you can do that. Like mentioned here:

Pipeline parsing and setting correct timestamp

Hello, I like to parse and set the correct timestamp to logmessages with the pipeline feature. I have all ready fields with hour,minutes,seconds, day of month and so on… My first pipeline stage is detecting the logs (for example application server type a). The second stage is parsing the logmessage with the proper grok pattern. Now I have the issue, that the logmessage timestamp and the graylog (elasticsearch) timestamp differ a view seconds. My idea is to use the parsed fields from stage two…

Other postings in the community will guide you!

[phil95 (phil)]

I’m searching since a while and i just found out this post that resolved my issue

Fortigate graylog modifies timestamp?

Timestamp is still +2 and timestamp in the logmessage still has Z behind it. [afbeelding] Using this now: rule “fortigate timestamp” when has_field(“devname”) && has_field(“date”) && has_field(“time”) then let build_message_0 = concat(to_string($message.date), " "); let build_message_1 = concat(build_message_0, to_string($message.time)); let new_timestamp = parse_date(value:to_string(build_message_1), pattern:“yyyy-MM-dd HH:mm:sss”, timezone:“Europ/Amstedam”); set_field(“timestamp”, ne…

Thanks a lot !!!