cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post

Using Alert Variables

Product Manager

Strangely enough, alert variables are one of the more straightforward features to configure in Orion's alerting engines.  Although they may seem a little confusing at first, they're really just a way to include relevant information in the messages that are sent when an alert is triggered or reset.  That's it.  These messages could be one of a number of things, like messages sent to the event log, or an email that's triggered when the alert fires.  That said, let's walk through the steps of configuring variables in an alert message.

When creating alerts in the Alert Manager, you can specify variables on the 'Trigger Actions' tab.

VM 2-2010-01-07-17-04-25.JPG

Here you can see we have two messages that will trigger when the alert fires: one to the event log, and an email.  Let's take a look at the event log message.

VM 2-2010-01-07-17-19-09.JPG

Here, we have specified the contents of the message to be written to the event log using two variables: ${NodeName} and ${Status}.  When the proper trigger conditions are met, an alert will fire that will write a message to the event log, and the message will tell us which node is affected as well as the status of the node. You can also specify variables in the same way when configuring an email to be sent when the alert triggers.

I'd also like to share a hint.  Not all of the variables available to you are displayed in the variable list in the Alert Manager.  For a complete list of variables, check out the appended Administration Guide which is posted here.

About the Author
Let me introduce myself.  My name is Craig McDonald, and I come from the land of video games and stock trading, sprinkled with identity management, and, by the way, I like to write.  Checkered past, you say?  How did you end up in network management, you ask?  Perfectly valid questions; I will connect the dots for you and it will all make sense shortly. I studied journalism at the University of Texas at Austin where I had the opportunity to write for The Daily Texan and Texas Monthly.  Upon graduation I was faced with two options: move to a small town and start my career at an even smaller newspaper, or make a home in Austin and see where this crazy tech town would take me.  I chose the latter, and ended up working in support and managing QA for a popular MMORPG called Ultima Online (this was before WoW was a sparkle in Blizzard's eye). After a few years of policing the haXXorZ, overseeing a few in-game weddings, and shipping several expansion skus, I decided it was time for a change.  I remember the advice from one of my journalism professors when I asked about pursuing a graduate degree; his suggestion, "Go to business school!"  I heeded his advice, got accepted to the McCombs School of Business at the University of Texas, and started working on my MBA. While finishing my MBA at McCombs, I was presented with an opportunity to work for a company that developed online trading software (Charles Schwab, formerly CyberTrader).  This may seem a stretch from video games, but the client/server infrastructure and the uptime requirements for an MMORPG and a securities trading engine are quite similar.  Although the content and use cases are obviously very different, both require fast connections and the ability to allow users to log into the service at any time.  My next career move was into the enterprise software arena where I worked as a product manager for Sun Microsystems in the Identity Management space. Fast forward to today, I'm your newest product manager at SolarWinds.  I will be managing Toolset, VoiP, and eventually the Kiwi products.  Outside of the SolarWinds 'Borg' (assimilation is swift and definitive), I keep busy with my lovely wife, two beautiful kiddos, and a pug named Marley.  When they go to bed, I'm either watching a movie, reading a book (working on Atlas Shrugged, and it is work, indeed), or staring at the red circle of death on my XBOX 360.