Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Orion custom properites and alerts: Refining alerts

Orion custom properites and alerts: Refining alerts

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,317 Votes: 0 Revisions: 8

Custom properties are often used to fit the management needs of a specific environment. This also allows the administrator to create and assign properties to nodes, interfaces and volumes.
It can be leveraged within advanced alerts to add environment-specific alert capabilities.

There are several built-in methods to define which elements an alert should apply to. If the qualifiers built onto Orion alerting would not define exactly the elements or conditions of interest, a custom property can be added.
In this case, the environment has several physical servers hosting several virtual servers. Both server types may be running a Windows 2003 or 2008 server and can be manufactured from three different vendors.
The naming convention of the servers does not indicate if a server is physical or virtual. There are also two different virtualization vendors used.

The following is an example where the Orion administrator needs to send an alert to the server administration department and the physical server hosting the virtual servers has less than 1 GB of available memory.
This case was derived from an actual use case.

1. Go to Start > All Programs > SolarWinds Orion > Grouping and Access Control > Custom Property Editor
    and create a new custom property based on the nodes to indicate that a node is a host to virtual machines.   

2. Check off the nodes that are known hosts.

    For more information about the Custom Property Editor, see Creating Custom Properties in the SolarWinds Network Performance Monitor Administrator Guide.

3. Create the alert and include the node custom property Is Host is equal to Yes.


The alert is actually quite simple now and fits the use case of defining physical servers as physical servers and is independent of the server manufacturer and virtualization vendor.
This allows the Orion administrator to control this qualifier. So if new vendors are used, it will not affect the alert capability as would happen if the alert was tied to a variable system qualifier.

For more information, please refer to Understanding Orion Advanced Alerts.

Applies to: NPM v11.0.1

Last modified