Splunk Search

Why does strptime not parse timestamps to nanoseconds (%9N/%9Q)?

andrewtrobec
Motivator

Splunk Enterprise 9.0.5.1

Hello!

I have to calculate the delta between two timestamps that have nanosecond granularity.  According to Splunk documentation nanoseconds are supported with either %9N or %9Q: https://docs.splunk.com/Documentation/Splunk/9.0.5/SearchReference/Commontimeformatvariables

andrewtrobec_0-1698327144862.png


When I try to parse a timestamp with nanosecond granularity, however, it stops at microseconds and calculates the delta in microseconds as well.  My expectation is that Splunk should maintain and manage nanoseconds.

Here is a run anywhere:

 

 

 

| makeresults
| eval start = "2023-10-24T18:09:24.900883123"
| eval end = "2023-10-24T18:09:24.902185512"
| eval start_epoch = strptime(start,"%Y-%m-%dT%H:%M:%S.%9N")
| eval end_epoch = strptime(end,"%Y-%m-%dT%H:%M:%S.%9N")
| table start end start* end*
| eval delta = end_epoch - start_epoch
| eval delta_round = round(end_epoch - start_epoch,9)

 

 

 


Is this a defect or am I doing something wrong?

Thank you!

Andrew

Labels (1)
0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

Looks like a defect to me

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 ...