Template:Objects

From NetXMS Wiki
Jump to navigation Jump to search

All network infrastructure monitored by NetXMS inside monitoring system represented as a set of objects. Each object represents one physical or logical entity (like host or network interface), or group of them. Objects organized into hierarchical structure. There are 30 different object classes:

Object Class Description Can contain
Entire Network Abstract object representing root of IP topology tree. All zone and subnet objects located under it. System can have only one object of this class.

If zoning enabled:

  • Zone

If zoning disabled:

  • Subnet
Zone Object representing group of (usually interconnected) IP networks without overlapping addresses. Contains appropriate subnet objects.
  • Subnet
Subnet Object representing IP subnet. Typically objects of this class created automatically by the system to reflect system's knowledge of IP topology.
  • Node
Node Object representing physical host or network device. These objects can be created either manually by administrator or automatically during network discovery process.
  • Interface
  • Network Service
  • VPN Connector
Cluster Object representing cluster consisted of two or more hosts.
  • Node
Interface Object representing network interface of node. These objects created automatically by the system during configuration polls. Nothing
Network Service Object representing network service running on a node (like http or ssh). Nothing
VPN Connector Object representing VPN tunnel endpoint. Such objects can be created to add VPN tunnels to network topology known y NetXMS server. Nothing
Service Root Abstract object representing root of your infrastructure service tree. System can have only one object of this class.
  • Cluster
  • Condition
  • Container
  • Mobile Device
  • Node
  • Subnet
Container Grouping object which can contain nodes, subnets, clusters, conditions, or other containers. With help of container objects you can build object's tree which represents logical hierarchy of IT services in your organization.
  • Cluster
  • Condition
  • Container
  • Mobile Device
  • Node
  • Subnet
Condition Object representing complicated condition – like "cpu on node1 is overloaded and node2 is down for more than 10 minutes". Nothing
Template Root Abstract object representing root of your template tree.
  • Template
  • Template Group
Template Group Grouping object which can contain templates or other template groups.
  • Template
  • Template Group
Template Data collection template. See Data Collection section for more information about templates.
  • Mobile Device
  • Node
Network Map Root Abstract object representing root of your network map tree.
  • Network Map
  • Network Map Group
Network Map Group Grouping object which can contain network maps or other network map groups.
  • Network Map
  • Network Map Group
Network Map Network map. Nothing
Dashboard Root Abstract object representing root of your dashboard tree.
  • Dashboard
Dashboard Dashboard. Can contain other dashboards.
  • Dashboard
Report Root Abstract object representing root of your report tree.
  • Report
  • Report Group
Report Group Grouping object which can contain reports or other report groups.
  • Report
  • Report Group
Report Report object. Nothing
Business Service Root Abstract object representing root of your business service tree. System can have only one object of this class.
  • Business Service
Business Service Object representing single business service. Can contain other business services, node links, or service checks.
  • Business Service
  • Node Link
  • Service Check
Node Link Link between node object and business service. Used to simplify creation of node-related service checks.
  • Service Check
Service Check Object used to check business service state. One business service can contain multiple checks. Nothing

Every object has set of attributes; some of them are common (like id and name), while other depends on object class – for example, attribute "SNMP community string" have only node objects.