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
Get Updates on the Splunk Community!

Dashboards: Hiding charts while search is being executed and other uses for tokens

There are a couple of features of SimpleXML / Classic dashboards that can be used to enhance the user ...

Splunk Observability Cloud's AI Assistant in Action Series: Explaining Metrics and ...

This is the fourth post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how ...

Brains, Bytes, and Boston: Learn from the Best at .conf25

When you think of Boston, you might picture colonial charm, world-class universities, or even the crack of a ...