I'm trying to generate events through an external script from the search, using the script command. Splunk says the command does not exist in commands.conf. However, the documentation for the script command doesn't say that the script needs to exist in commands.conf. Is this just a simple omission, or am I doing something wrong?
This is what I'm trying to do:
| script perl foo
I've not used the "script" command before, but I do use external scripts as custom commands. This involves setting up the "commands.conf" file.
Your script should live within the "bin" directory of your app, e.g.
$SPLUNK_HOME/etc/apps/<appName>/bin/, you should then add something like the following to the app's "local" directory...
[exampleCommand] filename = script.pl type = perl
You can then call the script in Splunk like the following assuming you have 2 arguments.
*| exampleCommand arg1 arg2
Yes, this is pretty much what is described in the documentation about custom commands in the documentation. The documentation for the script command led me to believe you can avoid editing commands.conf.
the documentation for the script command you can't use script like you are thinking.
script calls an external python program that can modify or generate search results. Scripts must be declared in the commands.conf file and be located in the $SPLUNKHOME/etc/apps//bin/ directory. The script is executed using $SPLUNKHOME/bin/python