Splunk Search

CSV _time differences depending on API call?

rvandolson
Loves-to-Learn

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

"2023-02-02T00:06:34.000-08:00"

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

yuanliu
SplunkTrust
SplunkTrust

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!

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...

Welcome to the Splunk Community!

(view in My Videos) We're so glad you're here! The Splunk Community is place to connect, learn, give back, and ...

Tech Talk | Elevating Digital Service Excellence: The Synergy of Splunk RUM & APM

Elevating Digital Service Excellence: The Synergy of Real User Monitoring and Application Performance ...