AutoPatrol, Bureaucrats, Administrators
683
edits
Difference between revisions of "UM:Objects"
→Overview
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:Objects}} | {{DISPLAYTITLE:Objects}} | ||
= Overview = | = Overview = | ||
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 | 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: | ||
{| class="wikitable" style="width: 70%" | {| class="wikitable" style="width: 70%" | ||
!width="15%"|Object Class | !width="15%"|Object Class | ||
!Description | !Description | ||
|- | |- | ||
| Entire Network || Abstract object representing root of IP topology tree. All subnet objects located under it. System can have only one object of this class. | | 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. | ||
|- | |||
| Zone || Object representing group of (usually interconnected) IP networks without overlapping addresses. Contains appropriate subnet objects. | |||
|- | |- | ||
| Subnet || Object representing IP subnet. Typically objects of this class created automatically by the system to reflect system's knowledge of IP topology. | | Subnet || Object representing IP subnet. Typically objects of this class created automatically by the system to reflect system's knowledge of IP topology. | ||
| Line 20: | Line 22: | ||
| VPN Connector || Object representing VPN tunnel endpoint. Such objects can be created to add VPN tunnels to network topology known y NetXMS server. | | VPN Connector || Object representing VPN tunnel endpoint. Such objects can be created to add VPN tunnels to network topology known y NetXMS server. | ||
|- | |- | ||
| Service Root || Abstract object representing root of your service tree. System can have only one object of this class. | | Service Root || Abstract object representing root of your infrastructure service tree. System can have only one object of this class. | ||
|- | |- | ||
| 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. | | 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. | ||
| Line 31: | Line 33: | ||
|- | |- | ||
| Template || Data collection template. See Data Collection section for more information about templates. | | Template || Data collection template. See Data Collection section for more information about templates. | ||
|- | |||
| Network Map Root || Abstract object representing root of your network map tree. | |||
|- | |||
| Network Map Group || Grouping object which can contain network maps or other network map groups. | |||
|- | |||
| Network Map || Network map. | |||
|- | |||
| Dashboard Root || Abstract object representing root of your dashboard tree. | |||
|- | |||
| Dashboard || Dashboard. Can contain other dashboards. | |||
|- | |||
| Report Root || Abstract object representing root of your report tree. | |||
|- | |||
| Report Group || Grouping object which can contain reports or other report groups. | |||
|- | |||
| Report || Report object. | |||
|- | |||
| Business Service Root || Abstract object representing root of your business service tree. System can have only one object of this class. | |||
|- | |||
| Business Service || Object representing single business service. Can contain other business services, node links, or service checks. | |||
|- | |||
| Node Link || Link between node object and business service. Used to simplify creation of node-related service checks. | |||
|- | |||
| Service Check || Object used to check business service state. One business service can contain multiple checks. | |||
|} | |} | ||