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!

Quantify Your Splunk Investment Impact: Introducing Savings Metrics to Value Insights

Building on the foundation established in our initial Value Insights releases, we are introducing the Savings ...

Event Series: Telemetry Pipeline Management

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...