Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Alert Action: Execute Script

I have created a home brew script that takes in a number of parameters. The script works as I use it with other alert actions with no problem. However, today when trying to set it up with a new alert it no longer sends the alert.

Here is the line that is in the "Program to Execute" box.

perl F:\noctools\scripts\cgi-bin\Alert.pl u "${NodeName}:${IfName} is ${Status} at ${LongDate} ${MediumTime}" "${NodeName}:${IfName} is ${Status} at ${LongDate} ${MediumTime}" jcavey2

My only guess as to why this one fails and the one below works is string length.

perl F:\noctools\scripts\cgi-bin\Alert.pl g "${NodeName}" "${NodeName}(${IP_ADDRESS}) is ${Status}." AG_OTTS_ORION_UP_DOWN

Is there a limit to the number of characters that can be used in this field?

Find more posts tagged with

Accepted answers

All comments

gbutler

Well I did a quick count... and you have 184 chars... I have a 197 chars (that is working).

Things to check...

1. If you did not export/import your action its REAL easy to get a typo in that little exe box. If I'm cutting and pasting I use an editor between pastes as a sanity check.

2. How do you know its not working? I ask this because because it may be running fine but the default user might be getting a authentication problem.

3. How are u testing? The test feature does nto work. The only reliable way I know to tests is to manually trip the monitor.

4. If you are not capturing errors an putting them into a log file... you might want to. I started doing this and its saved my bacon a bunch of times.

Good luck!

JasonKV

1. If you did not export/import your action its REAL easy to get a typo in that little exe box. If I'm cutting and pasting I use an editor between pastes as a sanity check.

I did both an import and export and I used and editor to check, double check, and tripple check the syntax. I even retyped it from scratch to make sure I had no mistakes. In addition I copied the exact execution statement and it ran perfectly in cmd.exe.

2. How do you know its not working? I ask this because because it may be running fine but the default user might be getting a authentication problem.

I know its not working because my alerting system is not recieving or sending out the alerts. It is not a permission issue because the same script call (different variables) works with out any problem.

3. How are u testing? The test feature does nto work. The only reliable way I know to tests is to manually trip the monitor.

I have tested both by tripping the alert and through the test button. Both do not work for the first script above, and both work with the second script listed above.

4. If you are not capturing errors an putting them into a log file... you might want to. I started doing this and its saved my bacon a bunch of times.

I will check log files and and see if I can find something in Orion log files. I really think the problem is between the triggering of the action and actually running the script.

Anyone else for thoughts?

gbutler

I'm not refering to Orion log files. I'm refering to having your script log errors to a local file. I don't think there is an Orion log file a that will help much for alert scripts.

Another thought. How are you determining whether your alert is triggering? What I do is I write an event to the event log as welll as I will watch the alert log table in the database. There you will see exactly when it triggers....etc..

JasonKV

I will write some log lines to see if my script is functioning, but I feel very confident from the combination of alerts and fires that I have done from both Orion and CMD.exe that its not my script.

I know its being fired because if I change my Execution scrip to the working one I get the alert, therefor the logic of getting it to fire is infact correct.

More to come as I try.

Please ...anyone. ..more thoughts... I beg you