Glossary

A persistent notification indicating a condition that requires operator attention. Alarms have a severity level (Normal, Warning, Minor, Major, Critical) and a lifecycle state (Outstanding, Acknowledged, Resolved, Terminated). See Alarms.

A lightweight service (nxagentd) installed on monitored systems. Collects metrics, executes actions, and reports data to the NetXMS server.

An object representing a group of nodes working together. NetXMS tracks cluster resources and performs resource-aware monitoring.

A periodic process that discovers and updates the configuration of managed nodes, including interfaces, software inventory, and supported capabilities.

An organizational object used to group other objects in the object tree.

A customizable visual layout that displays monitoring data — graphs, status indicators, alarm summaries, maps, and other elements. See Dashboards.

A single metric configured for collection on a node. Examples include CPU usage, disk space, and network traffic. See Data Collection Items.

An ordered set of rules that determine how NetXMS responds to events. Configured by administrators. See Events.

A notification generated by NetXMS when something significant occurs — a threshold is crossed, a node goes down, or a configuration changes. See Events.

A trouble ticket associated with an object, used to track the investigation and resolution of a problem. Incidents have states and comments, can be created manually or by event processing rules when an alarm is created, and are managed in the Incidents perspective.

A network interface of a managed device (Ethernet port, VLAN interface, loopback, etc.). Created automatically during configuration polls. See Interfaces.

An object state in which alarms and notifications are suppressed while polling and data collection continue. Events generated during maintenance are correlated to the maintenance event and skipped by event processing rules by default. See Maintenance Mode.

A result of measuring something on a monitored system, such as CPU usage or free disk space. Metrics are collected by DCIs.

A primary managed object representing a network device, server, or virtual machine. Nodes are the main targets for monitoring. See Nodes.

Any entity in the NetXMS object tree — nodes, containers, subnets, templates, dashboards, etc. See Objects.

The current condition of an object, indicated by color (green for Normal, red for Critical, etc.). Status propagates upward through the object tree. See Object Status.

A predefined operation (e.g., ping, traceroute, SSH connection, custom command) that can be executed on an object from its context menu. Object tools are configured by administrators.

A standard protocol for monitoring and managing network devices. NetXMS uses SNMP to collect data from switches, routers, firewalls, and other network equipment.

A periodic check of node reachability and operational status. Uses ICMP, agent, and SNMP checks to determine if a node is up or down.

An IP subnet object, usually created automatically from discovered interface addresses. Appears under the Entire Network root in the object tree. See Subnets.

A condition defined on a DCI that activates when the collected value crosses a specified boundary, generating an event.

The network connection layout showing how devices are physically (Layer 2) and logically (Layer 3) interconnected. See Topology.

A group of IP subnets forming a non-overlapping IP address space. Zone objects exist only when zoning is enabled on the server; remote zones are reached through zone proxy agents. See Zones.