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

Beta Alerting Engine: Trigger and Reset actions

Has anybody been able to get Beta Alerting Engines Trigger and Reset actions to work other than the mail and the logging?

I've tried to launch local executables (and sending Netsends just to verify that the alerts are in fact triggered) but I cannot get it to work.

In the "old" Orion, we launch an executable that forwards alerts to our SMS/Textmessaging server with GSM modems. The string also includes custom properties for the GSM-SMS server to decide on which on-callperson should get the alert, so it's somewhat complicated:

cmd /S /C ""d:\Program Files\Zonith\NMSListenerClient1.3\bin\sendAlarm.bat" -t "${Time}:${Second}CET - ALERT: ${ApplicationName} is ${Status}"" -u ${Location_Code} -a ${relevance}

For test purposes, I also tried to launch a simple Notepad.exe as a trigger event, but that didn't work either.

Yesterday, I spoke with Solarwinds Support and was told that if i check "allow to interact with desktop" on the "LogOn" tab of the properties of the "Solarwinds Alerting Engine" service on my server this problem would be resolved, but unfortunately it wasn't

I would love to hear some details of any success stories you may have out there on this subject

Lars Grabowski
Global Infrastructure
Chr. Hansen A/S

Currently using:
Cirrus Version 2.1 DL-500 Feb. 2006 (8.1.42)
Orion Application Monitor 7.8.82
Orion Web Engine Version 7.8.92
Orion NPM SLX 7.8.2 July 2005
Alert Manager 8.1.15

Find more posts tagged with

Accepted answers

All comments

dpezet

I can vouch for telephone paging using the NotePager Pro integration. I'll try launching a local executable and see what happens.

Don

dpezet

Just for a quick test I created a CMD file that executed:

dir c:\ > c:\test.txt

And set the new alert engine to run the CMD when a certain application was closed on one of my servers (we use the Application Monitor pack). I closed the application and a few minutes later I had a test.txt file on the SolarWinds server indicating proper execution. The added advantage of this test is that if an error did occur it would have been piped right into test.txt where I could read it.

You might want to try piping the output of your command into a text file to see what error it is returning.

Good luck,

Don

srazak

Hi,

Using the Alerting Engine Beta, I cannot get any alerts triggered. I've followed the manual and set up some test alerts on both application failure and node failure. I do not get the email, nor do I see any posting in the "Active Alerts" tab. The events that I am monitoring do show up in the "Current Events" screen.

My existing alerts continue to work fine in Orion.

Please help as I would like to get the Application alerts working.

I am currently using March 2006 realeases of:
Orion SLX
Application Monitor
Alerting Engine Beta

duncan_922

I just installed it today and it works pretty well. However I can trigger all alert actions (play a sound, flash color, text to speech, etc.) except sending e-mails. I am not using SMS though since our cel phones come with e-mail capability. Original alert e-mails from Orion work fine.