Alerting

unable to run python scripted alert

sbsbb
Builder

I've made a scripted alert in python, and put it in py app directory
.../splunk/etc/apps/myapp/bin/scripts/scripted_alert.py

in .../splunk/var/log/splunk/python.log I see that it has been triggered with the correct path, and parameters :
2014-08-22 14:37:01,178 INFO ['.../splunk/etc/apps/myapp/bin/scripts/scripted_alert.py', '1', '| stats c | eval ...

When I try to execute it with
.../splunk/bin/splunk cmd python .../splunk/etc/apps/myapp/bin/scripts/scripted_alert.py' with all the parameters from the python.log, it is working...

It seems that splunk is not taking the python interpreter ?
But in my file header I have

#!.../splunk/bin/python
# -*- coding: utf-8 -*-

(... is a substitution / I'm using Splunk 5.0.5)

0 Karma

starcher
Influencer

Most likely your hash bang is off. I believe in this case the full path should work better. if that is a typical Splunk unix install try:

#!/opt/splunk/bin/python

0 Karma

sbsbb
Builder

this is already the case

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!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...