It work the same as it does for scheduled or modular inputs. I have actual walk through and link to already made code in my git repo. http://www.georgestarcher.com/2014/02/16/splunk-alert-scripts-automating-control/
It work the same as it does for scheduled or modular inputs. I have actual walk through and link to already made code in my git repo. http://www.georgestarcher.com/2014/02/16/splunk-alert-scripts-automating-control/
yeah, it does indeed. I messed up by calling Intersplunk.getOrganizedResults() before reading from the stdin. And now I see that Intersplunk actually reads from stdin itself.
There was nothing special required for it to work and it does pass on stdio by design of Splunk. I have it working without issue on both Splunk v5 and Splunk v6. Is the hash bang at the the top of your alert script set to the correct path for your installation?
thanks, but looking at your alert_to_gsheet.py file, it seems like the session key is expected to be sent via stdin, which doesn't happen in my case. Do you have any special config that enables passing it? I tried setting 'passauth=true' in commands.conf, trying to trick it as if it was a search command and it still doesn't work: reading sys.stdin.readline() comes back empty...