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 Alert Macros

Have some of the macros changed in the beta alert engine? I can send alerts with ${CPULoad} and get the current CPU Load for a machine with the original alert engine, but when I attempt it with the beta, I always get 0% as the result.
I also use ${FullName} on the original, and it doesn't even recognize that one anymore. It sends the alert with ${FullName} instead of the data.

Thanks,
David

Find more posts tagged with

Accepted answers

All comments

Network_Guru

Have you tried using the SQL name for the node - ${node.caption} ?

Since this engine is based on SQL & using custom properties, it most likely needs to be formatted similar to queries you create with Report Writer.

-=Cheers=-
NG

coushatta

I tried ${node.caption} and it works for the name, but I can use ${NodeName} also, and that works for the name. My big problem is getting CPU Load to show. I keep getting 0%.

Any suggestions?

Thanks,
David

bleearg13

Thanks, NG! I was having the same issue and now it's resolved. I'm sure David will see the same thing if he tries it out.

One other problem I see is with the customization that SW put into the packaged Alert Engine. For instance, when one would choose to put the Interface Status macro in, the old engine would put Up, Down, Shutdown, etc. in the message that's sent out. However, the beta will enter the exact value, which means pretty much nothing to an end user when he/she sees "Your interface is currently 4." I could put a legend in, but that's just not graceful at all.

In addition, they've not included a way, yet, that one can get a page upon "Any time LastBoot changes" like the old engine. This was one of the few built-in alerts that we used on the old engine that we cannot replicate with the new one. Any ideas?

Grabowski

Coushatta,

Did you get this to work yet?

I am having exactly the same problems as you, but have not had any effect on the advice posted here by Network_Guru

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

coushatta

No I have not. I spoke with support and they told me that it was a known bug in the Beta Alert Engine. It will be fixed in the final release that comes with version 8.