Splunk Search

REST query via console vs API showing different results

bpenny
Explorer

Executive overview: We're using Splunk Cloud (Victoria Experience), and we're in the process of spinning up a new instance for FedRAMP purposes.

One thing I'm trying to do is streamline migrating of some of our custom sourcetypes from the existing environment to the new one. I'm able to perform a search via the console that returns a record containing all the details of a given sourcetype (This particular sourcetype has a few dozen EVAL-*, FIELDALIAS-*, and LOOKUP-* settings, so it's a pretty complex one.):

| rest /services/configs/conf-props | search title="sfdc:logfile"

 

If I try the above search via a POST to /services/search/v2/jobs/export (or the /servicesNS equivalent with either - wildcards or an explicit user & app) I don't get any of those EVAL-* etc. settings. The authentication token I'm using for the search was created by an admin user, and I've tried using that same admin user on the /servicesNS  requests. Why am I only getting partial results via the API?

Labels (2)
0 Karma
1 Solution

bpenny
Explorer

Turns out this was user error due to not parsing the results properly.

View solution in original post

bpenny
Explorer

Turns out this was user error due to not parsing the results properly.

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!

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas     Cisco Live 2026 is almost here, and this ...

What Is the Name of the USB Key Inserted by Bob Smith? (BOTS Hint, Not the Answer)

Hello Splunkers,   So you searched, “what is the name of the usb key inserted by bob smith?”  Not gonna lie… ...

Automating Threat Operations and Threat Hunting with Recorded Future

    Automating Threat Operations and Threat Hunting with Recorded Future June 29, 2026 | Register   Is your ...