I have several scheduled alerts set to trigger a script on every run. The scripts run CLI searches, and dump the output into our ticketing system. The scripts are triggering as expected, but the results from the alert triggered scripts are coming back with no data. However, when I trigger the same script manually for the same time frame, I get the results I expect. In the most recent test, I set the alert to trigger within a less than a minute of me running the script from the CLI. The window was set to 24 hours, and the alert triggered version produced a 0 byte file, and the CLI triggered version produced a 40kb file. Does anyone know why these differences might be showing up? The permissions are the same, I'm running the script from the CLI as the splunk user, and I'm using the same script in both the alert and the CLI. ... View more

I'm running into an issue with the syntax for a CLI search using erex. The problem seems to be with the double quotes. I've tried single quoting the erex examples and counter examples, but none of it seems effective. This search works in the GUI: index=name searchterm NOT otherterm |erex message examples="/foo/bar,/foobar" counterexamples="barfoo, foobar" |table item1,item2,item3,item4,item5 |uniq |sort item3 In the CLI, I've tried it a couple of different ways, and the closest I've gotten to a working search is: index=name searchterm NOT otherterm |erex message examples='/foo/bar,/foobar' counterexamples='barfoo, foobar' |table item1,item2,item3,item4,item5 |uniq |sort item3 the CLI search results in "INFO: No matching fields exist" Do any of you know what I'm doing wrong here? Thanks! ... View more