Vunetrix Manual: Group Settings

Group Name

Enter a meaningful name to identify the group. The name will be shown by default in the devices tree and in all alarms.

Status

Choose if monitoring for this group is started or paused. .We recommend using the default value. You can add additional tags to it, if you like.

• Started: Monitor this group.
• Paused: Pause monitoring for this group. All sensors on all devices in this group will be paused until this setting is changed again.

Tags

Enter one or more tags; confirm each tag by hitting space, comma, or enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case sensitive.

Priority

Select a priority for the group. This setting determines where the group will be placed in list views. Top priority will be at the top of a list. You can choose from one star (low priority) to five stars (top priority).

Sensor Management

Select which type of auto-discovery you would like to perform for this group. Choose between:

• Manual (no auto-discovery): Do not auto-discover any sensors, but only add sensors manually.
• Automatic device identification (standard, recommended): Use a small set of auto-discovery templates. This will scan your LAN and usually create a view standard sensors on your device.
• Automatic device identification (detailed, may create many sensors: Use an extended set of auto-discovery templates. This will scan your LAN and usually create many sensors on your device.
• Automatic sensor creation using specific device templates: Use specific auto-discovery templates only. Please select templates below. This will scan your LAN and add sensors defined in the template.

Device Template(s)

This option is only visible if using specific device templates (last option) is enabled above. Please choose one or more templates by adding a check mark in front of the respective template name. You can also select and deselect all items by using the check box in the table head. These will be used for auto-discovery on the current device. Choose from:

• ADSL
• Cisco ASA VPN
• Cisco Device (Generic)
• Dell MDI
• DNS Server
• Environment Jacarta
• Environment Poseidon
• Fritzbox
• FTP Server
• Generic Device (PING only)
• Generic Device (SNMP-enabled)
• Generic Device (SNMP-enabled, Detailed)
• HTTP Web Server
• Hyper V Host Server
• Linux/UNIX Device (SNMP or SSH enabled)
• Mail Server (Generic)
• Mail Server (MS Exchange)
• Microsoft Sharepoint 2010
• NAS LenovoEMC
• NAS QNAP
• NAS Synology
• NetApp
• NTP Server
• Printer (HP)
• RDP Server
• RMON compatible device
• Server (Compaq/HP agents)
• Server (Dell)
• Sever Cisco UCS
• Server IBM
• SonicWALL
• Switch (Cisco Catalyst)
• Switch (Cisco IOS Based)
• Switch (HP Procurve)
• UNIX/Linux Device
• UPS (APC)
• Virtuozzo Server
• VMware ESX / vCenter Server
• Windows (Detailed via WMI)
• Windows (via Remote Powershell)
• Windows (via WMI)
• Windows IIS (via SNMP)
• XEN Hosts
• XEN Virtual Machines
   

Once the auto-discovery is finished, Vunetrix will create a new ticket and list the device templates which were actually used to create new sensors. Templates which were not applied will not be shown in the ticket.

Discovery Schedule

Define when the auto-discovery will be run. Choose between:

• Once: Perform auto-discovery only once. New devices and sensors will be added once. You can run auto-discovery manually any time using an object's context menu.
• Hourly: Perform auto-discovery for new devices and sensors every 60 minutes. Note: Please use this option with caution! Frequently executed auto-discoveries might cause performance issues, especially when large network segments are scanned every hour.
• Daily: Perform auto-discovery for new devices and sensors every 24 hours. The first auto-discovery will run immediately, all other discoveries will start on the time defined in the Auto-Discovery Settings section of the System Administration—Monitoring settings.
• Weekly: Perform auto-discovery for new devices and sensors every 7 days. The first auto-discovery will run immediately, all other discoveries will start on the time defined in the Auto-Discovery Settings section of the System Administration—Monitoring settings.

IP Selection Method

Define how you want to define the IP range for auto-discovery. Choose between:

• Class C base IP with start/end (IPv4): Define an IPv4 class C address range.
• List of individual IPs and DNS names (IPv4): Enter a list of individual IPv4 addresses or DNS names.
• IP and Subnet (IPv4): Enter an IPv4 address and subnet mask.
• IP with octet range (IPv4): Enter an IPv4 address range for every IP octet individually. With this, you can define very customizable IP ranges.
• List of individual IPs and DNS names (IPv6): Enter a list of individual IPv6 addresses or DNS names.
• Use computers from the active directory (maximum 1000 computers): Search in the active directory for computers to perform auto-discovery.

Note: Only subnets with up to 65,536 IP addresses can be discovered! If you define a range with a higher number of addresses, discovery will stop before it is completed.

IPv4 Base

This field is only visible if Class C network detection is selected above. Enter a class C network as IP base for the auto-discovery. Enter the first three octets of an IPv4 IP address, for example, 192.168.0

IPv4 Range Start

This field is only visible if Class C network detection is selected above. Enter the IP octet of the class C network specified above from which Vunetrix will start the auto-discovery. This will complete the IP base above to an IPv4 address. For example, enter 1 to discover from 192.168.0.1.

IPv4 Range End

This field is only visible if Class C network detection is selected above. Enter the IP octet of the class C network specified above at which Vunetrix will stop the auto-discovery. This will complete the IP base above to an IPv4 address. For example, enter 254 to discover up to 192.168.0.254.

IPv4/DNS Name List
IPv6/DNS Name List

This field is only visible if the IP list option is selected above. Enter a list of IP addresses or DNS names which the auto-discovery will scan. Enter each address in a separate line.

IPv4 and Subnet (IPv4)

This field is only visible if the IP and subnet option is selected above. Enter an expression in the format address/subnet, e.g. 192.168.3.0/255.255.255.0. You can also use the short form like 192.168.3.0/24 in this example. Vunetrix will scan the complete host range (without network and broadcast address) defined by the IP address and the subnet mask.

IP with Octet Range

This field is only visible if the octet range option is selected above. Enter an expression in the format a1.a2.a3.a4, where a1, a2, a3, and a4 are each a number between 0-255, or a range with two numbers and a hyphen like 1-127. All permutations of all ranges are calculated, e.g. 10.0.1-10.1-100 results in 1,000 addresses that Vunetrix will scan during auto-discovery.

Organizational Unit

This field is only visible if active directory is selected above. Enter an organizational unit (OU) to restrict the active directory search to computers which are part of this OU. Just enter the name of the OU without any other term (i.e., without "OU" in front). If you leave this field empty, there will not be any restriction.

If you have sub-OUs, too, please consider the correct syntax in the format Y,OU=X: OUs that are part of another OU have to be listed together with their parent(s). Enter the sub-OU followed by ,OU= and the name of the parent OU. For example, assuming that the organizational unit 'Y' is part of the OU named 'X'. Then the syntax would be Y,OU=X. For three OUs 'X', 'Y' part of 'X', and 'Z' part of 'Y', the syntax would be Z,OU=Y,OU=X. Note that the order is important, sub-OUs have to be listed left of its according parents!

Name Resolution

Define how newly discovered devices will be monitored. This only affects new devices. The setting for existing devices will be kept. Choose between:

• Use DNS / WMI / SNMP names (recommended): Monitor newly discovered devices via their DNS, WMI, or SNMP names (if available).
• Use IP addresses: Monitor newly discovered devices via their IP address.

We recommend using the default value.

Device Rescan

Define if you want to rescan known devices. Choose between:

• Skip auto-discovery for known devices/IPs (recommended): Do not re-scan known devices or IP addresses, but only scan for new devices/IPs when auto-discovering. This can avoid re-creation of manually deleted sensors. Vunetrix will also avoid adding devices that are already included elsewhere in your configuration, e.g. in other groups.
• Perform auto-discovery for known devices/IPs: Re-scan known devices and IP addresses with every auto-discovery. This will re-create manually deleted sensors on existing devices.

We recommend using the default value.

Location (for geo maps)

When using geo maps using Google's API please enter a location in the first line. Objects will then be displayed on a geographical map with a flag, showing the current status using a color code similar to the sensor status icons (green - yellow - orange - red). You can enter a full postal address, city and country only, or latitude and longitude. It is possible to enter any text before, between, and after the coordinates, Vunetrix will parse latitude and longitude automatically; for example: 49.452778 11.077778 or enter 49.452778 any 11.077778 text

A minus sign (-) in the first line will hide an object from geo maps. In this case you can enter location information in line two and following.

You can define a specific label for each location: enter a string denoting the label in the first line and provide geo coordinates in the second line. This object will be displayed then with the label in Vunetrix's geo map.

Domain or Computer Name

Define the authority for Windows access. This is used for Windows Management Instrumentation (WMI) and other Windows sensors. If you want to use a Windows local user account on the target device, please enter the computer name here. If you want to use a Windows domain user account (recommended), please enter the (Active Directory) domain name here. If not explicitly defined, Vunetrix will automatically add a prefix in order to use the NT LAN Manager (NTLM) protocol. Please do not leave this field empty.

Username

Enter the username for Windows access. Usually, you will use credentials with administrator privileges.

Password

Enter the password for Windows access. Usually, you will use credentials with administrator privileges.

Username

Enter a login name for the access via SSH and WBEM. Usually, you will use credentials with administrator privileges.

Login

Define which authentication method will be used for login. Choose between:

• Login via Password: Provide a password for login. Enter below.

• Login via Private Key: Provide a private key for authentication. Note: Vunetrix can only handle keys in OpenSSH format which are not encrypted. You cannot use password protected keys here. In the text field, please paste the entire private key, including the "BEGIN" and "END" lines. Please make sure the according public key is provided on the target machine. For details, please see Monitoring via SSH.

Password

This field is only visible if password login is selected above. Enter a password for the Linux access via SSH and WBEM. Usually, you will use credentials with administrator privileges.

Private Key

This field is only visible if private key login is selected above. Paste a private key into the field (OpenSSH format, unencrypted). Usually, you will use credentials with administrator privileges. Note: If you do not insert a private key for the first time, but change the private key, you need to restart your Vunetrix core server service in order for the private key change to take effect! For details, please see Monitoring via SSH.

For WBEM Use Protocol

Define the protocol that will be used for WBEM. This setting is only relevant when using WBEM sensors. Choose between:

• HTTP: Use an unencrypted connection for WBEM.
• HTTPS: Use an SSL-encrypted connection for WBEM.

For WBEM Use Port

Define the port that will be used for WBEM. This setting is only relevant when using WBEM sensors. Choose between:

• Set automatically (port 5988 or 5989): Use one of the standard ports, depending on whether unencrypted or encrypted connection is chosen above.
• Set manually: Use a custom port. Define below.

WBEM Port

This setting is only visible if manual port selection is enabled above. Enter the WBEM port number.

SSH Port

Define the port number which will be used for SSH connections. Note: By default, this setting is automatically used for all SSH sensors, unless you define a different port number in the sensor settings.

SSH Rights Elevation

Define with which rights the command will be executed on the target system. Choose between:

• Run the command as the user connecting (default): Use the rights of the user who establishes the SSH connection.
• Run the command as another user using 'sudo': Use the rights of another user, for example, the administrator.
• Run the command as another user using 'su': Use the rights of another target user.

Target Username

This field is only visible if sudo or su is enabled above. Enter a username to run the specified command as another user than root. If you leave this field empty, the command will be run as root. Ensure that you set the Linux password even you use a public/private key for authentication.  This is not necessary if the user is allowed to execute the command without a password.

Password Target User

This field is only visible if su is enabled above. Enter the password for the specified target user.

User

Enter a login name for access to VMware and XEN servers. Usually, you will use credentials with administrator privileges.

Password

Enter a password for access to VMware and XEN servers. Usually, you will use credentials with administrator privileges.

VMware Protocol

Define the protocol used for the connection to VMware and XenServer. Choose between:

• HTTPS (recommended): Use an SSL-encrypted connection to VMware and XenServers.
• HTTP: Use an unencrypted connection to VMware and XenServers.

SNMP Version

Select the SNMP version that will be used for device connection. Choose between:

• v1: Use the simple standard v1 protocol for SNMP connections. This protocol only offers clear-text data transmission, but it is usually supported by all devices.
• v2c: Use the more advanced v2c protocol for SNMP connections. Data is still transferred as clear-text, but it supports 64-bit counters.
• v3: Use the latest v3 protocol for SNMP connections. It provides secure authentication and data encryption.

Note for SNMP v3: Due to internal limitations you can only monitor a limited number of sensors per second using SNMP v3. The limit is somewhere between 1 and 50 sensors per second (depending on the SNMP latency of your network). This means that using an interval of 60 seconds you are limited to between 60 and 3000 SNMP v3 sensors for each probe. If you experience an increased "Interval Delay" or "Open Requests" reading of the probe health sensor, you need to distribute the load over multiple probes. SNMP v1 and v2 do not have this limitation.

Community String

This setting is only visible if SNMP version v1 or v2c are enabled above. Enter the community string of your devices. This is a kind of "clear-text password" used for simple authentication. We recommend using the default value.

Authentication Type

This setting is only visible if SNMP version v3 is enabled above. Choose between:

• MD5: Use Message-Digest Algorithm 5 (MD5) for authentication.
• SHA: Use Secure Hash Algorithm (SHA) for authentication.

The chosen type has to match the authentication type of your device.

Note: If you do not want to use authentication, but you need SNMP v3, for example, because your device requires context, you can leave the field password empty. In this case, SNMP_SEC_LEVEL_NOAUTH will be used and authentication will be deactivated entirely.

User

This setting is only visible if SNMP version v3 is enabled above. Enter a username for secure authentication. This value has to match the username of your device.

Password

This setting is only visible if SNMP version v3 is enabled above. Enter a password for secure authentication. This value has to match the password of your device.

Encryption Type

This setting is only visible if SNMP version v3 is enabled above. Select an encryption type. Choose between:

• DES: Use Data Encryption Standard (DES) as encryption algorithm.
• AES: Use Advanced Encryption Standard (AES) as encryption algorithm.

The chosen type has to match the encryption type of your device.

Data Encryption Key

This setting is only visible if SNMP version v3 is enabled above. Enter an encryption key here. If you provide a key in this field, SNMP data packets will be encrypted using the encryption algorithm selected above, providing increased security. The provided key here has to match the encryption key of your device. Note: If the key entered in this field does not match the key configured in the target SNMP device, you will not get an error message! Please enter a string or leave the field empty.

Context Name

This setting is only visible if SNMP version v3 is enabled above. Enter a context name only if it is required by the configuration of the device. Context is a collection of management information accessible by an SNMP device. Please enter a string.

SNMP Port

Enter the port used for SNMP communication. We recommend using the default value.

SNMP Timeout (sec.)

Enter a timeout in seconds for the request. If the reply takes longer than this value the request is aborted and an error message is triggered.

When experiencing problems while monitoring via Windows sensors, you can set some compatibility options for trouble shooting.

Preferred Data Source

Define the method Windows sensors will use to query data. This setting is valid only for hybrid sensors offering performance counter and Windows Management Instrumentation (WMI) technology. The setting will be ignored for all other sensors! Choose between:

• Performance Counters and fallback to WMI (recommended): Try to query data via performance counters. If this is not possible, establish a connection via WMI. This is the recommended setting to best balance resource usage and functionality.

• Performance Counters only: Query data via performance counters only. If this is not possible, a sensor will return no data.

• WMI only: Query data via WMI only. If this is not possible, a sensor will return no data.

Timeout Method

Specify the time the sensor will wait for the return of its WMI query before aborting it with an error message. Choose between:

• Use 1.5x scanning interval (recommended): Use a default of one and a half times the scanning interval set for the sensor (see below in this settings).
• Set manually: Enter a timeout value manually.

We recommend using the default value. Only if you experience ongoing timeout errors, try increasing the timeout value.

Timeout Value (Sec.)

This field is only visible if the manual timeout method is selected above. Specify the time the sensor will wait for the return of its WMI query before aborting with an error message. Please enter an integer value.

When experiencing problems while monitoring via Simple Network Management Protocol (SNMP) sensors, you can set some compatibility options for trouble shooting.

SNMP Delay (ms)

Add a time in milliseconds that will be waited between two SNMP requests. This can help increase device compatibility. Please enter an integer value. We recommend using the default value. If you experience SNMP connection failures, please increase it. You can define a delay between 0 and 100, higher delays are not supported and will be discarded.

Failed Requests

Define if an SNMP sensor will try again after a request fails.

• Retry (recommended): Try again if an SNMP request fails. This can help prevent false error messages due to temporary timeout failures.
• Do not retry: Do not retry if an SNMP request fails. With this setting enabled an SNMP sensor will be set to error status earlier.

Overflow Values

Define how Vunetrix will handle overflow values. Some devices do not handle internal buffer overflows correctly. This can cause false peaks.

• Ignore overflow values (recommended): Ignore overflow values and do not include them in the monitoring data.
• Handle overflow values as valid results: Regard all overflow values as regular data and include them in the monitoring data.

We recommend using the default value. If you experience problems, change this option.

Zero Values

Define how Vunetrix will handle zero values. Some devices send incorrect zero values. This can cause false peaks.

• Ignore zero values for delta sensors (recommended): Ignore zero values and do not include them in the monitoring data.
• Handle zero values as valid results for delta sensors: Regard all zero values as regular data and include them in the monitoring data.

We recommend using the default value. If you experience problems, change this option.

32-bit/64-bit Counters

Define which kind of traffic counters Vunetrix will search for on a device.

• Use 64-bit counters if available (recommended): The interface scan will use 64-bit traffic counters, if available. This can avoid buffer overflows in the devices.
• Use 32-bit counters only: The interface scan will always use 32-bit traffic counters, even if 64-bit counters are available. This can lead to more reliable monitoring for some devices.

We recommend using the default value. If you experience problems, change this option.

Request Mode

Define which kind of request method Vunetrix uses for SNMP sensors.

• Use multi get (recommended): Bundle multiple SNMP requests into one request.
• Use single get: Use one request for each SNMP value. This can increase compatibility with older devices.

We recommend using the default value. If you experience problems, change this option.

Port Name Template

Define how the name of SNMP sensors created on a device will be put together. Enter a template using several variables. When adding new sensors, Vunetrix scans the interface for available counters at certain OIDs. At each OID usually several fields are available with interface descriptions. They are different for every device/OID. Vunetrix will use the information in these fields to name the sensors. If a field is empty or not available, an empty string is added to the name. As default, ([port]) [ifalias] is set as port name template, which will create a name such as (001) Ethernet1, for example. You can use any field names available at a certain OID of your device, among which are:

• [port]: The port number of the monitored interface.
• [ifalias]: The 'alias' name for the monitored interface as specified by a network manager, providing a non-volatile handling.
• [ifname]: The textual name of the monitored interface as assigned by the local device.
• [ifindex]: A unique value, greater than zero, for the monitored interface.
• [ifdescr]: A textual string containing information about the monitored device or interface, for example, manufacturer, product name, version.
• [ifspeed]: An estimate of the monitored interface's current bandwidth (KBit/s).

Combine them as you like to obtain suitable sensor names. See the More section below for more information about SNMP sensor names.

Port Name Update

Define how Vunetrix will react if you change port names in your physical device (e.g. a switch or router). Choose between:

• Keep port names (use this if you edit the names in Vunetrix): Do not automatically adjust sensor names. This is the best option if you want to change names in Vunetrix manually.

• Automatic sensor name update if name changes in device: If Vunetrix detects changes of port names in your physical device, it will try to automatically adjust sensor names accordingly. For detailed information please see More section below.

Port Identification

Define which field will be used for SNMP interface identification. Choose between:

• Automatic (recommended): Tries the ifAlias field first to identify an SNMP interface and then ifDescr. Note: ifName will not be tried automatically.
• Use ifAlias: For most devices ifAlias is the best field to get unique interface names.
• Use ifDescr: Use this option if the port order of your device changes after a reboot, and there is no ifAlias field available. For example, this is the best option for Cisco ASA devices. Note: When using this option it is important that your device returns unique interface names in the ifDescr field.
• Use ifName: You can also use this option if there is no unique ifAlias available. Note: When using this option it is important that your device returns unique interface names in the ifName field.
• No Port Update: Use this option to disable automatic port identification.

Start Port

For SNMP Traffic sensors, define at which port number Vunetrix will start to create sensors. Use 0 for automatic. We recommend using the default value.

End Port

For SNMP Traffic sensors, define at which port number Vunetrix will stop to create sensors. Use 0 for automatic. We recommend using the default value.

SNMP Debug Log

Define if you want to create an SNMP log file for debugging purposes. This is only recommended for debugging low level SNMP issues. Choose between:

• No log (recommended): No SNMP debug log file will be created.
• Enable debug log: An SNMP log file is written to the Logs (Debug) directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Data Storage section.

Proxy Settings for HTTP Sensors

HTTP Proxy Settings

The proxy settings determine how a sensor connects to a given URL. You can enter data for a proxy server that will be used when connecting via HTTP or HTTPS. Note: This setting is valid for the monitoring only and determines the behavior of sensors. In order to change proxy settings for the core server, please see System Administration—Core & Probes.

Name

Enter the IP address or DNS name of the proxy server to use. If you leave this field empty, no proxy will be used.

Port

Enter the port number of the proxy. Often, port 8080 is used. Please enter an integer value.

User

If the proxy requires authentication, enter the username for the proxy login. Note: Only basic authentication is available! Please enter a string or leave the field empty.

Password

If the proxy requires authentication, enter the password for the proxy login. Note: Only basic authentication is available! Please enter a string or leave the field empty.

Scanning Interval

Scanning Interval

The scanning interval determines the time the sensor waits between two scans. Select a scanning interval (seconds, minutes, or hours) from the list. You can change the available intervals in the system administration.

Cluster Usage

Scanning Distribution

This box is only visible if you're running a Vunetrix cluster. Sometimes you want to exclude a certain node from monitoring the sensors running on this probe, group, or device, for example, if a device is not reachable from every node configured in your cluster. In the list of cluster nodes, please select the nodes that will not be included in sensor scans. By default, this setting is inherited to all objects underneath.

Note: Inheritance for schedules, dependencies, and maintenance windows cannot be interrupted; the according settings from the parent objects will always be active. However, you can define additional settings here. They will be active in parallel to the parent objects' settings.

Schedule

Select a schedule from the list. Schedules can be used to pause monitoring for a certain time span (days, hours) throughout the week. You can create new schedules and edit existing ones in the account settings. Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active.

Maintenance Window

Specify if you want to set-up a one-time maintenance window. During a maintenance window this object and all child objects will not be monitored. They will enter a paused state then. Choose between:

• Not set (monitor continuously): No maintenance window will be set.
• Set up a one-time maintenance window: Pause monitoring within a maintenance window.

Maintenance Begins At

This field is only visible if maintenance window is enabled above. Use the date time picker to enter the start date and time of the maintenance window.

Maintenance Ends At

This field is only visible if maintenance window is enabled above. Use the date time picker to enter the end date and time of the maintenance window.

Dependency Type

Define a dependency type. Dependencies can be used to pause monitoring for an object depending on the status of another. You can choose between:

• Use parent: Pause the current object if its parent object is in a Down status, or if it is paused by another dependency.

• Select object: Pause the current object if its parent object is in a Down status, or if it is paused by another dependency. Additionally, pause the current object if a specific other object in the device tree is in a Down status, or if it is paused by another dependency. Select below.

Note: Testing your dependencies is easy! Simply choose Simulate Error Status from the context menu of an object that other objects depend on. A few seconds later all dependent objects should be paused.

Dependency

This field is only visible if the select object option is enabled above. Click on the reading-glass symbol and use the object selector to choose an object on which the current object will be dependent on.

Delay (Seconds)

Define a time span. After the master object for this dependency comes back to an Up status, monitoring of the depending objects will be additionally delayed by the defined time span. This can help avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Please enter an integer value in seconds.

Access Rights

User Group Access

Define which user group(s) will have access to the object you're editing. A table with user groups and right is shown; it contains all user groups from your setup. For each user group you can choose from the following access rights:

• Inherited: Use the settings of the parent object.
• None: Users in this group cannot see or edit the object. The object does not show up in lists and in the device tree. Exception: If a child object is visible to the user, the object is visible in the device tree, though not accessible.
• Read: Users in this group can see the object and review its monitoring results.
• Write: Users in this group can see the object, review its monitoring results, and edit the object's settings. They cannot edit access rights settings.
• Full: Users in this group can see the object, review its monitoring results, edit the object's settings, and edit access rights settings.

You can create new user groups in the System Administration—User Groups settings. To automatically set all objects further down in the hierarchy to inherit this object's access rights, set a check mark for the Revert children's access rights to inherited option.

For more details about access rights, please see section User Access Rights.

Channel Unit Configuration

Channel Unit Types

For each type of sensor channel, define the unit in which data is displayed. If defined on probe, group, or device level, these settings can be inherited to all sensors underneath. You can set units for the following channel types (if available):

• Bandwidth
• Memory
• Disk
• File
• Custom

Note: Custom channel types can be set on sensor level only.

Unusual Detection

Define if unusual detection is enabled for sensors. You can configure the behavior of unusual detection (or disable it completely) in the system settings.

• Enabled: Enable unusual detection for this group. Sensors in this group will turn to orange color if unusual activity is detected.
• Disabled: Disable unusual detection for this group. Unusual values will be ignored for sensors in this group; they will not show an unusual sensor status.

Similar Sensors Detection

Define if similar sensors detection is enabled for sensors. You can configure the depth of analysis of similar sensors detection (or disable it completely) in the system settings.

• Enabled: Enable similar sensors detection for this group. Sensors in this group will be considered during similarity analysis.
• Disabled: Disable similar detection for this group. Sensors in this group will not be taken into account during similarity analysis.

Sensor Limit

This setting allows the administrator to set a limit for the maximum number of sensors in this group. Subgroups are also included. If sensors exceed this limitation, they will be paused. This is of special interest for a Managed Service Provider (MSP). Choose between:

• Allow unlimited number of sensors: Disable a limitation of the number of sensors for this group. Any number of sensors can be added to this group.
• Limit number of sensors in this group: Enables a limitation of the number of sensors for this group. Only a limited number of sensors can be added to this group.

Maximum Number of Sensors

This field is only visible if limitation is enabled above. Define how many sensors can be added to this group. Please enter an integer value.