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

Use of Node Custom Properties in Group Applpication Dynamic Query

Use of Node Custom Properties in Group Applpication Dynamic Query

In short, would like to be able to evaluate node custom properties when creating a dynamic query in a group that is evaluating applications.

A couple examples of some custom properties we manage on nodes:

Whether the node is truly production, or is being staged, development only, etc...
What business system the server supports? (primarily in support of email systems?  manufacturing systems?  administrative systems? etc...)

We create groups that contain Applications monitoring these systems.
Right now, when creating a dynamic query where the Orion Object is an Application, node custom properties can not be evaluated.

Consider a hypothetical email system infrastructure with servers that have diverse naming conventions like 'mailserver1', 'popserver4', 'smtpserver2', etc...
There will likely be several that 'are production' and some that are just development or being staged.
It would be nice if I could create a single dynamic query that says:
Orion Object is Application, Node - Custom Property 1 is Production, & Node - Custom Property is EMail

Instead, I have the following work-around in place:

(several costly dynamic queries to achieve the goal)

Orion Object is Application, Node contains mailserver, Application Template begins with Production

Orion Object is Application, Node contains popserver, Application Template begins with Production

Orion Object is Application, Node contains smtpserver, Application Template begins with Production

To achieve this goal of having a group that shows all application monitors applied to all servers that support a particular system, and only those that are production, requires the following:
Management of copies of SAM templates with prefixes to differentiate prod from non-prod(being sure not to apply a 'Production-" prefixed template to a server that is not production.

Acknowledgement that some servers may get "missed"(not properly included in the group) if a different convention is used in the creation of a server, even if the appropriate 'system' custom property is properly set.

To some, this might sound like we're stretching how the product is used, or was designed for, but giving visibility to business groups of their systems like this has only increased the value of the product to our company.

2 Comments
Level 17

Hi gstadter,

You should be able to mitigate a lot of the pain around having to use naming conventions and wildcard searches on node names, etc by using Application Custom properties in your dynamic queries.

SAM-App-Custom-Property.png

You assign Application custom properties to Application Monitors (i.e.,instances of application monitor templates applied to nodes). HTH...some...until Node Custom properties can be leveraged as requested.

Level 13

Just gonna link to some other similar, duplicate, or related requests others have made.

PLEASE TAKE THE TIME TO GO VOTE THESE UP:

SolarWinds does listen to Feature Requests.  Just middle-click on each of the below links to open them in a new tab and vote them up.

I just opened up and voted on all of those (and several more) and the whole process took me 30 seconds, so please.  Vote.