"The page below is from the manual of PRTG, our quick-to-install and easy-to-use network monitoring software"

Try PRTG now and see how it can make your job easier.
 

Free Trial Download
You will be up and running in 2 minutes
Learn More
Screenshots, Features, Videos


Aurelio, System Admin at Paessler AG

On a probe's overview page, click on the Settings tab to change settings.

Add Remote Probe

You can add additional remote probes to your setup to extend you monitoring to networks that are not directly reachable by your PRTG core installation or cluster.

See Add Remote Probe for more details.

Probe Settings

The following settings are available in the Settings tab of every probe. As you may not need all of these for every probe, just regard those settings you really need, ignoring the others.

We recommend that you define as many settings as possible in the Root group, so you can inherit them to all other objects further down in the device tree hierarchy.

Note: This documentation refers to the PRTG System Administrator user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be visible in the way described here. When using a cluster installation, failover nodes are read-only by default.

Basic Probe Settings

Probe Name

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

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.

Status

Choose if monitoring for this probe is started or paused.

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

Priority

Select a priority for the probe. This setting determines where the probe 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).

Inherited Settings

By default, all following settings are inherited from objects higher in the hierarchy and should be changed there, if necessary. Often, best practice is to change them centrally in the Root group's settings. To change a setting only for this object, disable inheritance by clicking on the check mark before the corresponding setting name. You will then see the options described below.

Location

Location (for geo maps)

When you want to use Geo Maps, enter a location in the first line. Geographical maps will display objects (devices, groups) then 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, PRTG 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 geo marker will show then the object with the label in the PRTG geo map.

Credentials for Windows Systems

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, PRTG will automatically add a prefix in order to use the NT LAN Manager (NTLM) protocol. Please do not leave this field empty.

User

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.

Credentials for Linux/Solaris/Mac OS (SSH/WBEM) Systems

User

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

Login

Define the authentication method to use 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: PRTG can only handle keys in OpenSSH format which are not encrypted. You cannot use password protected keys here. In the text field, 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 you select password login 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 you select private key login 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 PRTG 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 to use for WBEM. This setting is only relevant if you use 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 to use for WBEM. This setting is only relevant if you use WBEM sensors. Choose between:

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

WBEM Port

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

SSH Port

Enter the port number to use for SSH connections.

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

SSH Rights Elevation

Define the rights with which you want to execute the command 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 User

This field is only visible if you choose sudo or su above. Enter a username to run the specified command as another user than root . If you leave this field empty, you will run the command as root. Ensure that you set the Linux password even if 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 you choose su above. Enter the password for the specified target user.

SSH Engine

Select the method you want to use to access data with SSH sensors. We strongly recommend that you keep the default engine! For some time you still can use the legacy mode to ensure compatibility with your target systems. Choose between:

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

Note: You can also individually select the SSH engine for each SSH sensor in the sensor settings.

Credentials for VMware/XenServer

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.

Note: Single Sign-On (SSO) passwords for vSphere do not support special characters. Please see the manual sections for VMware sensors for details.

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.

Session Pool

Define if you want to use session pooling for VMware sensors. Choose between:

  • Reuse session for 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 needs not to log in and out for each sensor scan. We recommend that you choose this option because it reduces network load and log entries on the target device, resulting in better 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. We recommend that you use the session pooling option above for better performance.

Credentials for SNMP Devices

SNMP Version

Select the SNMP version for the device connection. Choose between:

  • v1 : Use the simple v1 protocol for SNMP connections. This protocol only offers clear-text data transmission, but it is usually supported by all devices.
    Note: SNMP v1 does not support 64-bit counters which may result in invalid data when monitoring traffic via SNMP.
  • v2c (recommended) : Use the more advanced v2c protocol for SNMP connections. This is the most common SNMP version. Data is still transferred as clear-text, but it supports 64-bit counters.
  • v3 : Use the 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" with 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 you select SNMP version v1 or v2c above. Enter the community string of your devices. This is a kind of "clear-text password" for simple authentication. We recommend that you use the default value.

Authentication Type

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

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

The type you choose must 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 is used and authentication deactivated entirely.

User

This setting is only visible if you select SNMP version v3 above. Enter a username for secure authentication. This value must match the username of your device.

Password

This setting is only visible if you select SNMP version v3 above. Enter a password for secure authentication. This value must match the password of your device.

Encryption Type

This setting is only visible if you select SNMP version v3 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. Note: AES 192 and AES 256 are not supported by Net-SNMP because they lack RFC specification.

The type you choose must match the encryption type of your device.

Data Encryption Key

This setting is only visible if you select SNMP version v3 above. Enter an encryption key here. If you provide a key in this field, SNMP data packets are encrypted using the encryption algorithm selected above, which provides increased security. The key that you enter here must match the encryption key of your device.

Note: If the key you enter in this field does not match the key configured on the target SNMP device, you will not get an error message about this! Please enter a string or leave the field empty.

Context Name

This setting is only visible if you select SNMP version v3 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 for the SNMP communication. We recommend that you use the default value.

SNMP Timeout (Sec.)

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

Credentials for Database Management Systems

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

For Databases Use Port

Define which ports PRTG will use for connections to the monitored databases. Choose between:

  • Set automatically (default port, recommended): PRTG automatically determines the type of the monitored database and uses the corresponding default port to connect. See below for a list of default ports.
  • Define one custom port valid for all database sensors: Choose this option if your database management systems do not use the default ports. Define the port for database connections manually below. If you choose this option, PRTG will use the custom port for all database sensors.

If you choose the automatic port selection, PRTG uses the following default ports:

  • Microsoft SQL: 1433
  • MySQL: 3306
  • Oracle SQL: 1521
  • PostgreSQL: 5432

Port

Enter the number of the port that PRTG will use for database connections. Please enter an integer value.

Note: All your database sensors will use this port to connect!

Authentication

Select the authentication method for the connection to the SQL database. Choose between:

  • Windows authentication with impersonation : If you select this option, PRTG uses the Windows credentials as defined in the particular device settings for the database connection.
    Note: The user whose credentials are used needs to have permissions to log on to the system on which the PRTG probe with a database sensor runs. This is required for the impersonation.
  • SQL server authentication : Choose this option if you want to use explicit credentials for database connections.

User

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

Password

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

Timeout (Sec.)

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

Credentials for Amazon CloudWatch

Access Key

Enter your Amazon Web Services (AWS) Access Key. Please see the corresponding Amazon CloudWatch sensor documentation to know more about the rights that are required for querying AWS CloudWatch metrics.

Secret Key

Enter your Amazon Web Services (AWS) Secret Key. Please see the corresponding Amazon CloudWatch sensor documentation to know more about the rights that are required for querying AWS CloudWatch metrics.

Windows Compatibility Options

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 that you use 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.

SNMP Compatibility Options

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 that you use 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 PRTG 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 that you use the default value. If you experience problems, change this option.

Zero Values

Define how PRTG 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 that you use the default value. If you experience problems, change this option.

32-bit/64-bit Counters

Define which kind of traffic counters PRTG 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 that you use the default value. If you experience problems, change this option.

Request Mode

Define which kind of request method PRTG 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 that you use the default value. If you experience problems, change this option.

Note: PRTG uses paging for SNMP requests. This means that if a sensor has to query more than 20 OIDs, it will automatically poll the OIDs in packages of 20 OIDs each per request.

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, PRTG 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. PRTG 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.
  • [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).
  • [ifsensor]: The type of the sensor, this is SNMP Traffic or SNMP RMON . This is useful to differentiate between your SNMP Traffic and SNMP RMON sensors.

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 PRTG 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 PRTG) : Do not automatically adjust sensor names. This is the best option if you want to change names in PRTG manually.
  • Automatic sensor name update if name changes in device : If PRTG 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 Interface Index

For SNMP Traffic sensors, define at which index PRTG will start to query the interface range during sensor creation. Use 0 for automatic mode. We recommend that you use the default value.

End Interface Index

For SNMP Traffic sensors, define at which index PRTG will stop to query the interface range during sensor creation. Use 0 for automatic mode. We recommend that you use the default value.

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

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

When a Sensor Reports an Error

Define the number of scanning intervals that a sensor has time to report an error before the sensor will be set to a Down status. The sensor can try to reach a device several times, depending on the setup you can specify here, to help avoid false alarms if the monitored device has only temporary issues. For previous scanning intervals with failed requests, the sensor will show a Warning status. Choose between:

  • Set sensor to "down" immediately : The sensor will show an error immediately after the first failed request.
  • Set sensor to "warning" for 1 interval, then set to "down" (recommended) : After the first failed request, the sensor will show a yellow warning status. If the following request also fails, the sensor will show an error.
  • Set sensor to "warning" for 2 intervals, then set to "down" : Show an error status only after three continuously failed requests.
  • Set sensor to "warning" for 3 intervals, then set to "down" : Show an error status only after four continuously failed requests.
  • Set sensor to "warning" for 4 intervals, then set to "down" : Show an error status only after five continuously failed requests.
  • Set sensor to "warning" for 5 intervals, then set to "down" : Show an error status only after six continuously failed requests.

Note: Sensors that monitor via Windows Management Instrumentation (WMI) always wait at least one scanning interval until they show an error. It is not possible to set a WMI sensor "down" immediately, so the first option will not apply to these sensor types (all other options can apply).

Note: If a sensor has defined error limits for channels, this sensor will always be set to a Down status immediately, so no "wait" option will apply.

Note: If a channel uses lookup values, the sensor will always be set to a Down status immediately, so no "wait" options will apply.

Cluster Usage

Scanning Distribution

This box is only visible if you run a PRTG 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.

Schedules, Dependencies, and Maintenance Window

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.

Note: To terminate a current maintenance window before the defined end date, you can change the time in Maintenance Ends field to a date in the past.

Maintenance Begins

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

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. You can check all dependencies in your PRTG installation by selecting Devices | Dependencies from the main menu bar.

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.

Dependency Delay (Sec.)

This field is only visible if you select another object than the parent as dependency type. Define a time span in seconds for dependency delay. 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.

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 types of access rights 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 access rights settings of the parent object.
  • None : Users in this group cannot see or edit the object. The object neither shows up in lists nor 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 on access rights, please see the 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.

Advanced Network Analysis

Unusual Detection

Define if you want to benefit from unusual detection for sensors. You can configure the behavior of unusual detection (or disable it completely) in the system settings. Choose between:

  • Enabled : Activate unusual detection for this object and, by default, for all objects underneath in the hierarchy of the device tree. Sensors affected by this setting will turn to orange color (unusual sensor status) if PRTG detects unusual activity.
  • Disabled : Do not activate unusual detection. PRTG will ignore unusual values for sensors affected by this setting. These sensor will not show an unusual sensor status.

Similar Sensors Detection

Define if you want to activate Similar Sensors analysis. You can configure the depth of analysis of similar sensors detection (or disable it completely) in the system settings. Choose between:

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

System Information

Define if you want to retrieve and show System Information for your devices. Choose between:

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

Administrative Probe Settings / Probe Settings for Monitoring

Define the IP address used for outgoing monitoring requests.

  • If there is more than one IP on the current system available, you can specify the IP address that will be used for outgoing monitoring requests of certain sensor types.
  • The setting is valid for all monitoring requests sent from this PRTG probe.
  • This setting will be used for sensors using the following connection types: HTTP, DNS, FTP, IMAP, POP3, Port, Remote Desktop, SMTP, and SNMP. Note: This feature does not support all sensor types for technical reasons.
  • This is useful for devices that expect a certain IP address when queried.
  • Default setting is auto . PRTG will select an IP address automatically.

Note: If you change this setting, some sensors might stop working. For example, sensors might show a Down status if the selected IP address is blocked on the way to or directly on the monitored device.

Outgoing IPv4

Define the IP address for outgoing requests using the IPv4 protocol. The list shows all IP addresses available on the current system. Choose a specific IP address or select auto .

Outgoing IPv6

Define the IP address for outgoing requests using the IPv6 protocol. The list shows all IP addresses available on the current system. Choose a specific IP address or select auto . For details about the basic concept of IPv6 in PRTG, please see IPv6 section.

Cluster Connectivity

This box is only visible if you run a PRTG cluster. Define if this probe connects to all cluster nodes, including the failover nodes, or only to the primary master node. Choose between:

  • Probe sends data only to primary master node: The probe connects only to the primary master node. You are not able to review monitoring data on failover nodes. Consider to choose this option if you have bandwidth limitations in your network or if the probe cannot access your failover node(s).
  • Probe sends data to all cluster nodes: This is the default option. The probe connects to all nodes in your cluster and sends monitoring data to the failover node(s) in addition to the primary master. The probe is visible on all your nodes as soon as it connects automatically to the correct IP addresses and ports of the failover nodes. If your master node fails, you can still see monitoring data of this probe.
    Note: PRTG will not notify you if a remote probe is disconnected from a cluster node. Please check explicitly on a cluster node if your remote probes are connected (for example, via the device tree in the PRTG web interface on a cluster node).

Scheduled Restart settings

Restart Options

For best performance, we recommend that you regularly restart the Windows servers on which PRTG is running. To do this automatically for PRTG, you can schedule an automatic restart. Choose between the following options:

  • No scheduled reboot or service restart : Do not perform any scheduled restart of services automatically. We recommend a manual restart every few weeks. You can initiate a restart of your PRTG core server and probes under System Administration—Administrative Tools in the PRTG web interface.
  • Scheduled restart of PRTG services : Restart all PRTG services on the system where this probe runs on. If you choose this option on the local probe, the PRTG core server will restart as well. Define a schedule below.
  • Scheduled system reboot (recommended) : This is the recommended setting, although not set by default. Enter a schedule below. We recommend restarting Windows servers once a month for best performance.

Restart Schedule

This setting is only visible if you selected a schedule option above. Choose how often you want to restart PRTG services or the Windows server:

  • Once per week : Select a weekday and time below.
  • Once per month (recommended) : Select a day of month and time below.

Specify Day

This setting is only visible if you selected a schedule option above. Select a specific day of a week (Monday to Sunday ) resp. month (1st to 30th resp. Last ). If you select Last , the restart will always be executed on the last day of the month, regardless of how many days the month has.

Note: If you select a date that does not exist in every month (for example, the 30th day in February), PRTG will automatically initiate the restart on the last day of this month.

Specify Hour

This setting is only visible if you selected a schedule option above. Select the time of day when PRTG will perform the restart.

Note: A Windows warning message will be displayed 10 minutes before restart to inform a logged in user. The actual restart time can differ up to 30 minutes from the settings you enter below!

Click Save to store your settings. If you change tabs or use the main menu, all changes to the settings will be lost!

Notifications

The status or the data of a sensor can trigger notifications. Using this mechanism, you can configure external alerting tailored to you needs. In an object's detail page, click on the Notifications tab to change sensor notification triggers. The defined triggers will be inherited down to sensor level. For detailed information, please see Sensor Notifications Settings section.

Others

For more general information about settings, please see Object Settings section.

More

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

Knowledge Base: How can I add my own device icons for use in the PRTG web interface?

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

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

Ajax Web Interface—Device and Sensor Setup—Topics

Other Ajax Web Interface Sections

Copyright © 1998 - 2016 Paessler AG