|
Is it possible for a custom search script to launch another splunk search? I've been looking over the docs and sources for the However, if I attempt to acutually launch a search using the
I've done some logging in my search command to confirm that the search command is working and that I'm getting a different If I hard code a call to Is this a bug, a feature? Any ideas? Things I've tried:
|
|
This appears to be a bug when running a search as a separate process. It appears that we create a session key for that process but not the main splunkd process. Could you try your custom search command with a search like "| metadata hosts | mysearchcommand" and see if it works? Stephen, you are correct. I can successfully launch a search from my custom search script if the first search command is
(03 Jun '10, 15:25)
Lowell ♦
I tried running my search command from a saved search that was set with
(03 Jun '10, 20:59)
Lowell ♦
Unfortunately there's no good workaround until we fix this. It is scheduled to arrive in 4.1.4.
(04 Jun '10, 16:51)
Stephen Sorkin ♦
Thanks Stephen. Guess I'll have to hard-code the login info in the script (or in a password file) for the time being... I'll be looking forward to 4.1.4. BTW, is there a SPL number for this issue?
(04 Jun '10, 17:26)
Lowell ♦
This is tracked by SPL-31148.
(06 Jun '10, 02:31)
Stephen Sorkin ♦
I can confirm that the 4.1.4 release fixed this issue for me. It is now possible to execute a saved search from a search command!
(02 Aug '10, 20:23)
Lowell ♦
showing 5 of 6
show 1 more comments ▼
|
