PRTG Manual: Root Group Settings

The root group is the highest instance in the object hierarchy and it is the parent to most other objects. Therefore, most objects inherit settings from the root group. So, before you create your own sensors, it is a good idea to review the root group's settings to make sure that they suit your needs.

i_round_blueIf necessary, you can override every setting for every single child object. To do so, disable the respective Inherit option of an object.

Root Group Settings

The following settings are available on the Settings tab. All of the settings that you define here can be inherited to all other objects in your setup.

i_round_blueThis documentation refers to an administrator that accesses the PRTG web interface on a master node. Other user accounts, interfaces, or failover nodes might not have all of the options in the way described here. In a cluster, note that failover nodes are read-only by default.

In this section:

Basic Group Settings

Setting

Description

Group Name

Enter a meaningful name to identify the group. By default, PRTG displays it in the device tree.

Status

Select the monitoring status of the group:

  • Started: Monitor the group.
  • Paused: Pause monitoring for the group. All sensors on all devices in the group are in the Paused status until you change this setting.

Location

Setting

Description

Location (for Geo Maps)

If you want to use Geo Maps, enter a location in the first line. Geographical maps then display objects like devices or groups with a status icon 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, as PRTG automatically parses latitude and longitude, for example, enter 49.452778 11.077778, or enter 49.452778 any 11.077778 text.

A minus sign (-) in the first line hides an object from a geographical map. 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 the coordinates in the second line. This geographical marker then shows the object with the label in the geographical map.

i_round_blueThe preview map always has a road map layout regardless of the map layout you set in User Interface.

Credentials for Windows Systems

Setting

Description

Domain or Computer Name

Enter 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, enter the computer name. If you want to use a Windows domain user account (recommended), enter the (Active Directory) domain name. If If you do not explicitly define it, PRTG automatically adds a prefix to use the NT LAN Manager (NTLM) protocol. Do not leave this field empty.

User

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

Password

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

Credentials for Linux/Solaris/macOS (SSH/WBEM) Systems

Setting

Description

User

Enter a login name for the access via Secure Shell (SSH) and Web-based Enterprise Management (WBEM). Usually, you use credentials with administrator rights.

Login

Select the authentication method to use for the login:

  • Login via Password: Provide a password for the login.
  • Login via Private Key: Provide a private key for authentication.
    i_round_redPRTG can only handle keys in the OpenSSH format that are not encrypted. You cannot use password-protected keys. Paste the entire private key, including the BEGIN and END lines. Make sure that a corresponding public key exists on the target device. For details, see section Monitoring via SSH.

Password

This setting is only visible if you enable Login via Password above. Enter a password for the Linux access via SSH and WBEM. Usually, you use credentials with administrator rights.

Private Key

This setting is only visible if you enable Login via Private Key above. Paste a private key into the field (OpenSSH format, unencrypted). Usually, you use credentials with administrator rights.

i_round_redIf you are not inserting a private key for the first time but instead, you want to change the private key, you need to restart the PRTG core server service for the private key change to take effect. For details, see section Monitoring via SSH.

For WBEM Use Protocol

i_round_blueThis setting is only relevant if you use WBEM sensors.

Select the protocol to use for WBEM:

  • HTTP: Use an unsecure connection for WBEM.
  • HTTPS: Use a Secure Sockets Layer (SSL)/Transport Layer Security (TLS) secured connection for WBEM.

For WBEM Use Port

i_round_blueThis setting is only relevant if you use WBEM sensors.

Select how to set the port to use for WBEM:

  • Set automatically (port 5988 or 5989): Use one of the default ports. The default port for unsecure connections is 5988 and the default port for secure connections is 5989.
  • Set manually: Use a custom port.

WBEM Port

This setting is only visible if you enable Set manually above. Enter the WBEM port number.

SSH Port

Enter the port number to use for SSH connections. The default port is 22.

i_round_blueBy default, PRTG automatically uses this setting for all SSH sensors unless you define a different port number in the sensor settings.

SSH Rights Elevation

Select the rights that you want to use to execute the command on the target system:

  • Run the command as the user connecting (default): Use the rights of the user who establishes the SSH connection, as defined above.
  • Run the command as another user using 'sudo' (with password): Use the rights of another user with a password required for sudo to run commands on the target system, for example, as root user.
  • Run the command as another user using 'sudo' (without password): Use the rights of another user without a password required for sudo to run commands on the target system, for example, as root user.
  • Run the command as another user using 'su': Use the rights of another user with su to run commands on the target system.

Target User

This setting is only visible if you select a sudo or su option above. Enter a username to run the specified command as a user other than root. If you leave this field empty, you run the command as root. Make sure that you set the Linux password even if you use a public key or a private key for authentication. This is not necessary if the user is allowed to execute the command without a password.

Password

This setting is only visible if you choose to run the commands using su or sudo with password above. Enter the password for the specified target user.

SSH Engine

Select the method that you want to use to access data with SSH sensors:

i_round_redWe strongly recommend that you use the default SSH engine. For now, you can still use the legacy mode to ensure compatibility with your target systems.

  • Default (recommended): This is the default monitoring method for SSH sensors. It provides the best performance and security.
  • Compatibility Mode (deprecated): Try this legacy mode only if the default mode does not work on the target system. The compatibility mode is the SSH engine that PRTG used in previous versions and it is deprecated. We will remove this legacy option soon, so try to get your SSH sensors to run with the default SSH engine.

i_round_blueYou can also individually select the SSH engine for each SSH sensor in the sensor settings.

Credentials for VMware/XenServer

Setting

Description

User

Enter a login name for access to VMware and Xen servers. Usually, you use credentials with administrator rights.

Password

Enter a password for access to VMware and Xen servers. Usually, you use credentials with administrator rights.

i_round_bluesingle sign-on (SSO) passwords for vSphere do not support special characters. See the sections for VMware sensors for details.

VMware Protocol

Select the protocol to use for the connection to VMware and XenServer:

  • HTTPS (recommended): Use a Secure Sockets Layer (SSL)/Transport Layer Security (TLS) secured connection.
  • HTTP: Use an unsecure connection.

Session Pool

Select if you want to use session pooling for VMware sensors:

  • Reuse session for multiple scans (recommended): Select this option to use session pooling. With session pooling, a VMware sensor uses the same session as created in advance to query data and does not need to log in and out for each sensor scan. We recommend that you use this option because it reduces network load and log entries on the target device, which can increase performance.
  • Create a new session for each scan: If you select this option and disable session pooling, a VMware sensor has to log in and out for each sensor scan, which can decrease performance.

Credentials for SNMP Devices

Setting

Description

SNMP Version

Select the Simple Network Management Protocol (SNMP) version for the device connection:

  • v1: Use SNMP v1 for the connection. SNMP v1 only offers clear-text data transmission.
    i_round_redSNMP v1 does not support 64-bit counters. This might result in invalid data when you monitor traffic via SNMP.
  • v2c (recommended): Use SNMP v2c for the connection. SNMP v2c also only offers clear-text data transmission but it supports 64-bit counters.
  • v3: Use SNMP v3 for the connection. SNMP v3 provides secure authentication and data encryption.
    i_round_redIf you select v3, you can only monitor a limited number of sensors per second because of internal limitations. The limit is somewhere between 1 and 50 sensors per second (depending on the SNMP latency of your network). This means that a scanning interval of 60 seconds limits you to between 60 and 3000 SNMP v3 sensors per probe. If you see an increase in Interval Delay or Open Requests with the Probe Health sensor, distribute the load over multiple probes. v1 and v2 do not have this limitation.

Community String

This setting is only visible if you select v1 or v2c above. Enter the community string of your devices. This is like a clear-text password for simple authentication. We recommend that you use the default value.

Authentication Type

This setting is only visible if you select v3 above. Select the authentication type:

  • MD5: Use message-digest algorithm 5 (MD5) for authentication.
  • SHA: Use Secure Hash Algorithm (SHA) for authentication.

i_round_blueIf you do not want to use authentication but you need SNMP v3, for example, because your device requires context, you can leave Password empty. In this case, PRTG uses SNMP_SEC_LEVEL_NOAUTH and it entirely deactivates authentication.

i_round_redThe authentication type you select must match the authentication type of your device.

User

This setting is only visible if you select v3 above. Enter a username for secure authentication.

i_round_redThe username that you enter must match the username of your device.

Password

This setting is only visible if you select v3 above. Enter a password for secure authentication.

i_round_redThe password that you enter must match the password of your device.

Encryption Type

This setting is only visible if you select v3 above. Select an encryption type:

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

i_round_blueNet-SNMP does not support AES-192 and AES-256. They do not have RFC specifications.

i_round_redThe encryption type that you select must match the encryption type of your device.

Data Encryption Key

This setting is only visible if you select v3 above. Enter an encryption key. If you provide a key, PRTG encrypts SNMP data packets with the encryption algorithm that you selected above, which provides increased security. Enter a string or leave the field empty.

i_round_redThe encryption key that you enter must match the encryption key of your device. If the encryption keys do not match, you do not get an error message.

Context Name

This setting is only visible if you select v3 above. Enter a context name only if the configuration of the device requires it. Context is a collection of management information that is accessible by an SNMP device. Enter a string.

SNMP Port

Enter the port for the SNMP communication. The default is 161. We recommend that you use the default value.

Timeout (Sec.)

Enter a timeout in seconds for the request. Enter an integer value. If the reply takes longer than this value, the sensor cancels the request and triggers an error message. The maximum timeout value is 300 seconds (5 minutes).

Credentials for Database Management Systems

The settings you define in this section apply to the following sensors:

Setting

Description

Port for Databases

Select the port PRTG uses for connections to the monitored databases:

  • Set automatically (default port, recommended): PRTG automatically determines the type of the monitored database and uses the corresponding default port to connect. PRTG uses the following default ports:
    • Microsoft SQL: 1433
    • MySQL: 3306
    • Oracle SQL: 1521
    • PostgreSQL: 5432
  • Define one custom port valid for all database sensors: Select this option if your database management systems do not use the default ports. Enter the port for database connections below. If you select this option, PRTG uses the custom port for all database sensors.

Custom Database Port

Enter the number of the custom port that PRTG uses for database connections. Enter an integer value.

i_round_bluePRTG uses this port for all database sensors that inherit this setting.

Authentication Mode

Select the authentication mode for the connection to the Structured Query Language (SQL) database:

  • Windows authentication with impersonation: PRTG uses the Windows credentials that you define in settings that are higher in the object hierarchy (for example, in the settings of the parent device) for the database connection.
    i_round_redThe user whose credentials are used needs to have permission to log on to the probe system with a database sensor. This is necessary for the impersonation.
  • SQL server authentication: Use explicit credentials for database connections.

User

This setting is only visible if you enable SQL server authentication above. Enter the username for the database connection.

Password

This setting is only visible if you enable SQL server authentication above. Enter the password for the database connection.

Timeout (Sec.)

Enter a timeout in seconds for the request. Enter an integer value. If the reply takes longer than this value, the sensor cancels the request and triggers an error message. The maximum timeout value is 300 seconds (5 minutes).

Credentials for AWS

i_square_cyanFor more information about the permissions that are necessary to query the AWS API, see the Knowledge Base: How do I set permissions for the Amazon Web Services (AWS) API key to use certain sensors in PRTG?

Setting

Description

Access Key

Enter your Amazon Web Services (AWS) access key.

Secret Key

Enter your AWS secret key.

Windows Compatibility Options

If you experience problems when you monitor via Windows sensors, use the following compatibility options for troubleshooting.

Setting

Description

Preferred Data Source

i_round_blueThis setting only applies to hybrid sensors that use both performance counters and Windows Management Instrumentation (WMI). The setting does not apply to other sensors.

Define the method that Windows sensors use to query data:

  • Performance Counters and fallback to WMI: Try to query data via performance counters. If this is not possible, establish a connection via WMI.
  • Performance Counters only: Query data via performance counters only. If this is not possible, the sensor returns no data.
  • WMI only (recommended): Query data via WMI only. If this is not possible, the sensor returns no data. We recommend that you use this option.

Timeout Method

Select the time that the sensor waits for the return of the WMI query before the sensor cancels the query and shows an error message:

  • Use 1.5x scanning interval (recommended): Multiply the scanning interval of the sensor by 1.5 and use the resulting value.
  • Set manually: Manually enter a timeout value. We recommend that you use the default value.
    i_round_blueIf you experience ongoing timeout errors, try increasing the timeout value.

Timeout (Sec.)

This setting is only visible if you enable Set manually above. Enter the time the sensor waits for the return of its WMI query before it cancels it and shows an error message. Enter an integer value. The maximum value is 900 seconds (15 minutes).

SNMP Compatibility Options

If you experience problems when you monitor via Simple Network Management Protocol (SNMP) sensors, use the following compatibility options for troubleshooting.

Setting

Description

SNMP Delay (ms)

Enter the time in milliseconds that PRTG waits between two SNMP requests. This can increase device compatibility. Enter an integer value. We recommend that you use the default value. You can define a delay between 0 and 100. PRTG does not support higher delays.
i_round_blueIf you experience SNMP connection failures, try increasing the delay.

Failed Requests

Select if an SNMP sensor tries again after a request fails:

  • Retry (recommended): Try again if an SNMP request fails. This can prevent false error messages because of temporary timeout failures.
  • Do not retry: Do not retry if an SNMP request fails. If you select this option, an SNMP sensor shows a Down status earlier.

Overflow Values

Select how PRTG handles overflow values. Some devices do not correctly handle internal buffer overflows. This can cause false peaks.

  • Ignore overflow values: Ignore overflow values and do not include them in the monitoring data. We recommend that you use this option.
  • Handle overflow values as valid results: Regard all overflow values as regular data and include them in the monitoring data.

i_round_blueIf you experience problems because of strange peaks in your data graphs, change this option. Peaks might indicate that the monitored device resets counters without an overflow. PRTG interprets such behavior as overflow that results in data peaks. Select the option Ignore overflow values in this case. For more details, see the Knowledge Base: What is the Overflow Values setting in the SNMP Compatibility Options?

Zero Values

Select how PRTG handles 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. We recommend that you use this option.
    i_round_blueIf you experience problems, try changing this option.
  • Handle zero values as valid results for delta sensors: Regard all zero values as regular data and include them in the monitoring data.

32-bit/64-bit Counters

Select the type of traffic counters that PRTG searches for on a device:

  • Use 64-bit counters if available (recommended): The interface scan uses 64-bit traffic counters, if available. This can avoid buffer overflows in the devices. We recommend that you use the default value.
    i_round_blueIf you experience problems, try changing this option.
  • Use 32-bit counters only: The interface scan always uses 32-bit traffic counters, even if 64-bit counters are available. This can make monitoring more reliable for some devices.

Request Mode

Select the request method that PRTG uses for SNMP sensors:

  • Use multi get (recommended): Bundle multiple SNMP requests into one request. We recommend that you use this option.
    i_round_blueIf you experience problems, try changing this option.
  • Use single get: Use one request for each SNMP value. This can increase compatibility with older devices.

i_round_bluePRTG uses paging for SNMP requests. This means that if a sensor has to query more than 20 object identifiers (OID), it automatically polls the OIDs in packages of 20 OIDs each.

Walk Mode

Select the kind of SNMP walk that PRTG uses for SNMP sensors:

  • Use GETBULK requests (recommended): Request the next x OIDs in one SNMP request. The default value is 10. It is dynamic based on the response size.
    i_round_redThis option only works with devices that support SNMP version v2c or higher. Make sure that you set the correct SNMP Version in the Credentials for SNMP Devices settings of the parent device or inherit it from objects that are higher in the object hierarchy.
  • Use GETNEXT requests: Request one OID at a time. This can increase compatibility with older devices or with devices that have insufficient SNMP BULKWALK support.

Port Name Template

Select how PRTG displays the name of SNMP sensors. Enter a template that uses several variables. When you add new sensors, PRTG scans the interface for available counters at certain OIDs. At each OID, several fields with interface descriptions are usually available. They are different for every device and OID. PRTG uses the information in these fields to name the sensors. If a field is empty or if it is not available, PRTG adds an empty string to the name. By default, the port name template is ([port]) [ifalias] [ifsensor], which creates a name like (001) Ethernet1 Traffic. You can use and combine any field names that are available at an OID of your device, for example:

  • [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.
  • [ifdescr]: A textual string containing information about the monitored device or interface, for example, manufacturer, product name, or version.
  • [ifspeed]: An estimate of the monitored interface's current bandwidth (Kbit/s).
  • [ifsensor]: The type of the sensor, this is Traffic or RMON. This helps to differentiate between SNMP Traffic and SNMP RMON sensors.

i_square_cyanFor more information about SNMP sensor names, see the Knowledge Base: How can I change the defaults for names automatically generated for new SNMP sensors?

Port Name Update

Select how PRTG reacts if you change the names of ports in your physical device (for example, a switch or router):

  • Keep port names (use this if you edit the names in PRTG): Do not automatically adjust sensor names. This is the best option if you want to manually change names in PRTG.
  • Automatic sensor name update if name changes in device: If PRTG detects port name changes in your physical device, it tries to automatically adjust the sensor names accordingly.

i_square_cyanFor more information about automatic name updates, see the Knowledge Base: Automatically update port name and number for SNMP Traffic sensors when the device changes them

Port Identification

Select the field that PRTG uses for SNMP interface identification:

  • Automatic identification (recommended): Try the ifAlias field first to identify an SNMP interface and then try ifDescr.
    i_round_bluePRTG does not automatically try ifName.
  • Use ifAlias: For most devices, ifAlias is the best field to use for unique interface names.
  • Use ifDescr: Use this option if the port order of your device changes after a restart, and if no ifAlias field is available. For example, this is the best option for Cisco ASA devices.
    i_round_blueIf you use 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 no unique ifAlias is available.
    i_round_blueIf you use this option, it is important that your device returns unique interface names in the ifName field.
  • Do not update ports: Use this option to disable the automatic port identification.

Start Interface Index

i_round_blueThis setting only applies to SNMP Traffic sensors and to Cisco IP SLA sensors.

Enter the index at which PRTG starts to query the interface range during sensor creation. Enter 0 for the automatic mode. We recommend that you use the default value.

End Interface Index

i_round_blueThis setting only applies to SNMP Traffic sensors and to Cisco IP SLA sensors.

Enter the index at which PRTG stops querying the interface range during sensor creation. Enter 0 for the automatic mode. We recommend that you use the default value.

Proxy Settings for HTTP Sensors

The proxy settings determine how a sensor connects to a URL. You can enter data for an HTTP proxy server that sensors use when they connect via HTTP or HTTPS.

i_round_blueThis setting only applies to HTTP sensors and how they monitor. To change the proxy settings for the PRTG core server, see section Core & Probes.

i_round_blueThe SSL Certificate sensor and the SSL Security Check sensor do not support HTTP proxies but you can configure connections via SOCKS proxies in the sensors' settings.

Setting

Description

Name

Enter the IP address or Domain Name System (DNS) name of the proxy server. If you leave this field empty, HTTP sensors do not use a proxy.

Port

Enter the port number of the proxy. The default is 8080. Enter an integer value.

User

If the proxy requires authentication, enter the username for the proxy login.

i_round_redOnly basic authentication is available. Enter a string or leave the field empty.

Password

If the proxy requires authentication, enter the password for the proxy login.

i_round_redOnly basic authentication is available. Enter a string or leave the field empty.

Scanning Interval

Setting

Description

Scanning Interval

Select a scanning interval from the dropdown list. The scanning interval determines the amount of time that the sensor waits between two scans. Choose from:

  • 30 seconds
  • 60 seconds
  • 5 minutes
  • 10 minutes
  • 15 minutes
  • 30 minutes
  • 1 hour
  • 4 hours
  • 6 hours
  • 12 hours
  • 1 day

i_round_blueYou can change the available intervals in the system administration on PRTG on premises installations.

If a Sensor Query Fails

Select the number of scanning intervals that the sensor has time to reach and to check a device again if a sensor query fails. Depending on the option that you select, the sensor can try to reach and to check a device again several times before the sensor shows the Down status. This can avoid false alarms if the monitored device only has temporary issues. For previous scanning intervals with failed requests, the sensor shows the Warning status. Choose from:

  • Set sensor to down immediately: Set the sensor to the Down status immediately after the first request fails.
  • Set sensor to warning for 1 interval, then set to down (recommended): Set the sensor to the Warning status after the first request fails. If the second request also fails, the sensor shows the Down status.
  • Set sensor to warning for 2 intervals, then set to down: Set the sensor to the Down status only after the third request fails.
  • Set sensor to warning for 3 intervals, then set to down: Set the sensor to the Down status only after the fourth request fails.
  • Set sensor to warning for 4 intervals, then set to down: Set the sensor to the Down status only after the fifth request fails.
  • Set sensor to warning for 5 intervals, then set to down: Set the sensor to the Down status only after the sixth request fails.

i_round_blueSensors that monitor via Windows Management Instrumentation (WMI) always wait at least one scanning interval before they show the Down status. It is not possible to immediately set a WMI sensor to the Down status, so the first option does not apply to these sensors. All other options can apply.

i_round_blueIf you define error limits for a sensor's channels, the sensor immediately shows the Down status. None of the interval options apply.

i_round_blueIf a channel uses lookup values, the sensor immediately shows the Down status. None of the interval options apply.

Schedules, Dependencies, and Maintenance Window

Setting

Description

Schedule

Select a schedule from the list. You can use schedules to monitor during a certain time span (days or hours) every week. Choose from:

  • None
  • Saturdays
  • Sundays
  • Weekdays
  • Weekdays Eight-To-Eight (08:00 - 20:00)
  • Weekdays Nights (17:00 - 09:00)
  • Weekdays Nights (20:00 - 08:00)
  • Weekdays Nine-To-Five (09:00 - 17:00)
  • Weekends

i_square_cyanYou can create schedules, edit schedules, or pause monitoring for a specific time span. For more information, see section Schedules.

Maintenance Window

Select if you want to set up a one-time maintenance window. During a maintenance window, monitoring stops for the selected object and all child objects. They show the Paused status instead. Choose between:

  • Not set (monitor continuously): Do not set up a one-time maintenance window. Monitoring is always active.
  • Set up a one-time maintenance window: Set up a one-time maintenance window and pause monitoring. You can define a time span for a the pause below.

i_round_blueTo close an active one-time maintenance window before the end date, select Not set (monitor continuously).

Maintenance Begins

This setting is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the start date and time of the one-time maintenance window.

Maintenance Ends

This setting is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the end date and time of the one-time maintenance window.

Access Rights

Setting

Description

User Group Access

Select the user groups that have access to the object. You see a table with user groups and group access rights. The table contains all user groups in your setup. For each user group, you can choose from the following group access rights:

  • Inherited: Inherit the access rights settings of the parent object.
  • No access: Users in this user group cannot see or edit the object. The object neither shows up in lists nor in the device tree.
    i_round_blueThere is one exception: If a user in this user group has access to a child object, the parent object is visible in the device tree but users in this user group cannot access it.
  • Read access: Users in this group can see the object and view its monitoring results. They cannot edit any settings.
  • Write access: Users in this group can see the object, view its monitoring results, and edit its settings. They cannot edit its access rights settings.
  • Full access: Users in this group can see the object, view its monitoring results, edit its settings, and edit its access rights settings.

To automatically set all child objects to inherit this object's access rights, enable the Revert children's access rights to inherited option.

i_square_cyanFor more details on access rights, see section Access Rights Management.

Channel Unit Configuration

Setting

Description

Channel Unit Types

For each type of channel, select the unit in which PRTG displays the data. If you define this setting 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

i_round_blueCustom channel types are only available on sensor level.

Advanced Network Analysis

Setting

Description

Unusual Detection

Select if you want to use the unusual detection for sensors:

  • Enabled: Activate the unusual detection for this object and, by default, for all objects underneath in the object hierarchy. Sensors that are affected by this setting show the Unusual status if PRTG detects unusual activity.
  • Disabled: Do not activate the unusual detection. PRTG ignores unusual values for sensors that are affected by this setting. These sensors do not show the Unusual status.

i_round_blueYou can configure the behavior of the unusual detection or completely disable it in the system settings.

Similar Sensors Detection

Select if you want to activate the similar sensors analysis:

  • Enabled: Activate the similar sensors detection for this object and, by default, for all objects underneath in the object hierarchy. PRTG considers all sensors that are affected by this setting during the similarity analysis.
  • Disabled: Do not the activate the similar sensors detection. PRTG does not consider sensors that are affected by this setting during the similarity analysis.

i_round_blueYou can configure the depth of the analysis of the similar sensors detection or completely disable it in the system settings.

System Information

Select if you want to retrieve and show system information for your devices:

  • Enabled: Activate the system information feature for this object and, by default, for all objects underneath in the hierarchy.
  • Disabled: Do not activate the system information feature.

i_round_blueSystem Information is enabled by default. To retrieve the data, PRTG automatically uses the credentials for Windows systems and the credentials for SNMP devices in the device settings or as inherited from a parent object like the root group. Consider this when you monitor devices that are outside of the local network, especially when you use SNMP v1 or SNMP v2c, which do not provide encryption.

i_podThis setting is not available on the hosted probe of a PRTG hosted by Paessler instance.

i_round_redSave your settings. If you change tabs or use the main menu without saving, all changes to the settings are lost.

More

i_square_blueKNOWLEDGE BASE

How does PRTG compute CPU Index, Traffic Index and Response Time Index?

How can I change the defaults for names automatically generated for new SNMP sensors?

Automatically update port name and number for SNMP Traffic sensors when the device changes them

What is the Overflow Values setting in the SNMP Compatibility Options?

Device and Sensor Setup