Getting Data In

syntax for scripted input in inputs.conf

bfaber
Communicator

Am I correct in thinking that

[script://./bin/runmycmd.sh cmd]

will not work?

I'd like to be able to hand the variable cmd to runmycmd...

Tags (1)
0 Karma
1 Solution

ziegfried
Influencer

You can parameterize the scripted inputs. I've used this several times. So if you configure the scripted input this way

[script://./bin/runmycmd.sh cmd]

the value "cmd" will be avaiable to the script in the variable $1.

View solution in original post

ziegfried
Influencer

You can parameterize the scripted inputs. I've used this several times. So if you configure the scripted input this way

[script://./bin/runmycmd.sh cmd]

the value "cmd" will be avaiable to the script in the variable $1.

bfaber
Communicator

This worked. A warning for all, 'cmd' had to be the full path to the cmd file. For instance $SPLUNK_HOME/etc/apps/appname/bin/cmd

Thanks!

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...