Where can custom properties be defined in NPM?

Where can custom properties be defined in NPM?

• A. Devices in the cloud only
• B. Dashboards only
• C. Nodes or interfaces
• D. Alerts module

Answer: (C)

Custom properties are extra metadata you attach to the objects NPM monitors to store organization-specific information. In NPM, these properties are defined for the actual inventory objects that hold performance data, primarily network nodes (devices) and their interfaces. By adding custom properties to a node or to an interface, you can capture details like location, owner, asset tags, or any other attribute you need and then use that data in reports, filters, and alerting. Dashboards are for displaying data, not for defining new metadata, and the alerts module uses existing properties (including any custom ones) to trigger alerts rather than defining the properties themselves. Cloud or on-prem devices don’t change where you define these fields—the definition happens on the monitored objects themselves, hence nodes or interfaces.

Custom properties are extra metadata you attach to the objects NPM monitors to store organization-specific information. In NPM, these properties are defined for the actual inventory objects that hold performance data, primarily network nodes (devices) and their interfaces. By adding custom properties to a node or to an interface, you can capture details like location, owner, asset tags, or any other attribute you need and then use that data in reports, filters, and alerting. Dashboards are for displaying data, not for defining new metadata, and the alerts module uses existing properties (including any custom ones) to trigger alerts rather than defining the properties themselves. Cloud or on-prem devices don’t change where you define these fields—the definition happens on the monitored objects themselves, hence nodes or interfaces.