Getting Data In

go's time.RFC3339Nano format

framirez_enova
Explorer

Anyone having issues with nano second formatting from JSON logs. Currently it seems like times get rounded up or something.

What's sent:      2020-09-11T10:23:44.30373164-05:00
What shows:     9/11/20 10:23:44.000 AM

If you have/experienced this issue, how are you coping with or how did you solved it?

Labels (3)
0 Karma

framirez_enova
Explorer

Interesting on the digit. Will keep that in mind.   I also reached out to splunk support and they advise to try this in the props.conf file for the source:

%Y-%m-%dT%H:%M:%S.%9N%:z

0 Karma

isoutamo
SplunkTrust
SplunkTrust
%F <=> %Y-%m-%d
%T <=> %H:%M:%S

Please check your source is there eight or nine digits and use based on that %8N or %9N otherwise this didn't work.
0 Karma

isoutamo
SplunkTrust
SplunkTrust
I think that _time field can show it only ms not with more digits. If you want see all then you must convert it to anther field e.g. eval fullTime = strftime(_time, “%FT%T.%8N%:z”)
You have only 8 digits on your example even ns have 9, maybe this can also affect here?
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...