Alerting

Why does my alert script fail on windows?

jameshgibson
Path Finder

I have spent most of the afternoon trying to work out why the script doesn't seem to work. From the logs I found in %SPLUNK_HOME%\var\log\splunk\ the commmand will never work as long as my search command contains quotes, braces, >, < or & anywhere. e.g

C:\WINDOWS\system32\cmd.exe /c " "pathtosplunk\Splunk\bin\scripts\myscript.py" "49" "index="my_index" ("some" OR "other") | rex field=blah "(?<breakage>.*)" commands" "name_of saved search" "Saved Search [nameofsavedsearch] number of events(99)" "http://path toresults" "" "path\\to\\csv" "

Is there any solution?

Tags (2)
0 Karma

jameshgibson
Path Finder

The only way I have managed to get this working is by re-writing %SPLUNK_HOME%\etc\apps\search\bin\runshellscript.py

Clearly this is not a good solution and will break after any update.

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

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...