Difference between revisions of "UM:Basic Concepts"

← Older edit

UM:Basic Concepts (view source)

Revision as of 18:13, 13 September 2022

2,301 bytes removed , 18:13, 13 September 2022

m

Text replacement - "^" to "{{deprecated}}"

AlexKirhenshtein

AutoPatrol, Bureaucrats, Administrators

481

edits

@@ Line 1: / Line 1: @@
-{{DISPLAYTITLE:Basic Concepts}}
+{{deprecated}}{{DISPLAYTITLE:Basic Concepts}}
 = Overview of System Architecture =
@@ Line 17: / Line 17: @@
 = Objects =
-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 12 different object classes:
+{{Objects}}
-{| class="wikitable" style="width: 60%"
-! width="20%"|Object class|| 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.
-|-
-| Subnet || Object representing IP subnet. Typically objects of this class created automatically by the system to reflect system's knowledge of IP topology.
-|-
-| Node || Object representing physical host or network device. These objects can be created either manually by administrator or automatically during network discovery process.
-|-
-| Cluster || Object representing cluster consisted of two or more hosts.
-|-
-| Interface || Object representing network interface of node. These objects created automatically by the system during configuration polls.
-|-
-| Network Service || Object representing network service running on a node (like http or ssh).
-|-
-| VPN Connector || Object representing VPN tunnel endpoint. Such objects can be created to add VPN tunnels to network topology known by NetXMS server.
-|-
-| Service Root || Abstract object representing root of your 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.
-|-
-| Condition || Object representing complicated condition – like "cpu on node1 is overloaded and node2 is down for more than 10 minutes".
-|-
-| Template Root || Abstract object representing root of your template tree.
-|-
-| Template Group || Grouping object which can contain templates or other template groups.
-|-
-| Template || Data collection template. See Data Collection section for more information about templates.
-|}
-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.
 = DCI (Data Collection Items) =
@@ Line 83: / Line 51: @@
 = Thresholds =
-Each threshold is a combination of condition and events pair — if condition becomes true, associated "activation" event generated, and when it's becomes false again, "deactivation" event generated. Thresholds let you take a proactive approach to network management. You can define thresholds for any data collection items that you are monitoring. When setting thresholds, first determine what would constitute reasonable thresholds. To decide on a threshold value, you need to know what is normal value and what is out of range. Only you can decide what is normal behavior for a device on your network. Generally, we recommend that you collect information about a device throughout one complete business cycle, before determining the normal high/low range. Consider collecting values such as error rates, retry limits, collisions, throughput, relation rates, and many more. You also have the possibility to define more than one threshold for a single DCI, which allows you to distinguish between different severity conditions.
+Each threshold is a combination of a condition and an events pair. If a condition becomes true, associated "activation" event generated, and when it's becomes false again, "deactivation" event generated. Thresholds let you take a proactive approach to network management. You can define thresholds for any data collection items that you are monitoring. When setting thresholds, first determine what would constitute reasonable thresholds. To decide on a threshold value, you need to know what is normal value and what is out of range. Only you can decide what is normal behavior for a device on your network. Generally, it's recommended that you collect information about a device throughout one complete business cycle, before determining the normal high/low range. Consider collecting values such as error rates, retry limits, collisions, throughput, relation rates, and many more. You also have the possibility to define more than one threshold for a single DCI, which allows you to distinguish between different severity conditions.
 = Events and Alarms =