Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Creating an Orion Web Console custom property produces unexpected results

Creating an Orion Web Console custom property produces unexpected results

Created by John.Orteza, last modified by MindTouch on Jun 23, 2016

Views: 87 Votes: 1 Revisions: 14

Overview

After you create and enable a custom property, the Manage Alerts screen does not display alert data.

Environment

NPM version 11.5

Cause 

The name you assigned to the custom property is:

  • A default system name (such as Type)
  • A preexisting field name used in another field 

The Orion web interface prevents you from creating a custom property using a default system property name (such as EnableLevel, or Frequency). However, if you enter Type for the property name, the web interface allows you to continue, generating a blank white screen on the Manage Alerts Option screen.

8.PNG

Resolution

When you create a custom property, do not enter a default system name (such as Type) or a preexisting field name for the Property Name field, as shown below.

10.png 

See Default system properties of a SolarWinds Orion installation for a list of default system property names used in the Orion web interface.

 

Last modified

Tags

Classifications

Public