Splunk Enterprise

unable to extract timestamp till nano seconds

ips_mandar
Builder

Hi
I am trying to extract timestamp including nanoseconds but I am able to extract only 7 digits of nanoseconds though I used %9N in TIME_FORMAT.
Below is my sample event-

 

 

10,11/03/20 04:00:00.00000010,11/03/20,04:00:00,Zx: 6037,04:00:00,48d4c21c3014850838840a460424c05b20412128053ce6074720006e00f1ff5500000000000000,Mod=2,AckReq=0,RtBits=0,MsgSeq=35,OnRte=1,Id=46,VId=6037

 

 

Below is my props.conf -

 

 

[abc_logs_st]
LINE_BREAKER = ([\r\n]+)
SHOULD_LINEMERGE = false
NO_BINARY_CHECK = true
category = Custom
pulldown_type = 1
disabled = false
TIME_PREFIX = ^\d+\,
MAX_TIMESTAMP_LOOKAHEAD = 30
TIME_FORMAT = %m/%d/%y %H:%M:%S.%9N

 

 

Why Splunk is considering only 7 digits after decimal..Is this bug in Splunk?


 Thanks.

Labels (1)
Tags (2)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

The example event has only 8 digits after the decimal.

---
If this reply helps you, Karma would be appreciated.
0 Karma

ips_mandar
Builder

@richgalloway  No this won't help.
Even if I include 9 digits after decimal still splunk was able to extract 7 digits only .
Is this bug with Splunk?

0 Karma
Get Updates on the Splunk Community!

Upcoming Webinar: Unmasking Insider Threats with Slunk Enterprise Security’s UEBA

Join us on Wed, Dec 10. at 10AM PST / 1PM EST for a live webinar and demo with Splunk experts! Discover how ...

.conf25 technical session recap of Observability for Gen AI: Monitoring LLM ...

If you’re unfamiliar, .conf is Splunk’s premier event where the Splunk community, customers, partners, and ...

A Season of Skills: New Splunk Courses to Light Up Your Learning Journey

There’s something special about this time of year—maybe it’s the glow of the holidays, maybe it’s the ...