Splunk Search

CSV _time differences depending on API call?


When I manually run a Splunk search via the API as follows:

curl "https://host:8089/services/search/v2/jobs" -d search='search query...'  -d max_count=0 -d earliest_time=xxx -d latest_time=now

curl "https://host:8089/services/search/v2/jobs/jobid/results/" --get -d output_mode=csv -d count=0

I get timestamps like this for the _time column


When I run the same query, just as a saved search:

curl "https://host:8089/servicesNS/nobody/search/search/v2/jobs/export?output_mode=csv -d search='savedsearch "Saved Search"'

I get timestamps like this for the _time column

"2023-02-06 00:00:00.000 PST"

How can I make the latter look like the former so Excel can ingest it properly?

Labels (1)
0 Karma


The best I can get is to make a field named time instead of _time in that saved search.

| eval time = replace(strftime(_time, "%FT%H:%M:%S.%Q%z"), "(\d\d)$", ":\1")

Alternatively, if Excel (why?) can accept a space between the time string and the timezone string,

| eval _time = replace(strftime(now(), "%FT%H:%M:%S.%Q %z"), "(\d\d)$", ":\1")

SPL seems to be quite insistent on how internal fields are presented even if you convert it to string.

Tags (1)
0 Karma
Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...