Splunk Dev

Custom Search Command (V2/Chunked): Persist script

spunk_enthusias
Path Finder

Hi! Long time listener, first time caller here.

Our custom search command needs some slow initialization, which we would prefer to skip on repeated calls.

Is there a way to keep the process alive after the first invocation and only call dispatch() afterwards?
Something that does what scripttype = persist does for REST endpoints.

My understanding is that the protocol would allow this.

Calling dispatch() in a loop sadly doesn't work - would've been too easy, huh?
(It does work in so far that the command finishes - it's just that the script gets started again the next time)

0 Karma
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!

Accelerate Splunk App Development with AI

  Learn how to automate the repetitive parts of your build cycle.   Watch On-Demand   Replay the Accelerate ...

Splunk Agent Observability: Measuring AI Value with Splunk Tokenomics on AWS

The AI landscape is moving faster than ever, and our latest 2026 State of Observability report provides the ...

Enterprise Security Watch Party: What’s New in 8.8 - Recap

Splunk Community HQ hosted a Splunk Enterprise Security Watch Party: What’s New In ES 8.8 last Thursday. I had ...