PRTG Manual: System Administration—Core & Probes

To open the system administration, select Setup | System Administration from the main menu bar. Select the various tabs to change the different settings.

System Administration Bar

System Administration Bar

You can define the following aspects of your PRTG system setup:

In the core and probe management settings, you can define settings for the core server as well as for probe connections if you use remote probes or mini probes.

icon-i-round-redIf you cannot save changes to Core & Probes settings because you get an Error (Bad Request) with the message Active Directory Domain not accessible, ensure that you provide the correct access type for your domain in section Active Directory Integration. For example, change "local user" to Use explicit credentials and provide correct credentials for the domain. PRTG automatically sets the access type "local system" by default, so you might need to change this.

icon-prtg-on-premisesIf you use PRTG on premises and open the system administration page from another administration page, PRTG asks you to enter your credentials again for security reasons if 15 minutes (900 seconds) have passed since your last credential-based login. A dialog box appears. Enter your Login Name and Password for PRTG in the corresponding fields and confirm to continue.

Core and Probes Settings

icon-i-roundThis documentation refers to the PRTG System Administrator user accessing the PRTG web interface on a master node. If you use other user accounts, interfaces, or nodes, you might not see all of the options in the way described here. If you use a cluster installation, note that failover nodes are read-only by default.

Proxy Configuration

icon-prtg-on-demandThis option is not available in PRTG hosted by Paessler.

Use Proxy Server

We recommend that you use PRTG with a direct internet connection. However, if you need to use a proxy, you can configure the relevant settings here. Choose between:

  • No, use direct connection to the internet (default): Do not use a proxy. Use this setting if a direct internet connection to the server running the PRTG core server is available.
  • Yes, in our network a proxy is mandatory: Define proxy settings below.

icon-i-roundProxy settings are valid for Auto-Update, Activate the Product, obtaining Geo Maps tiles, and for sending out HTTP, push, and SMS text message Notifications.

Proxy Server

This setting is only visible if you enable Yes, in our network a proxy is mandatory above. Enter the address of the proxy server that you use for outbound connections. Enter a valid address.

Port

This setting is only visible if you enable Yes, in our network a proxy is mandatory above. Enter the port number of the proxy server that you use for outbound connections. Enter an integer value.

Use Proxy Credentials

This setting is only visible if you enable Yes, in our network a proxy is mandatory above. Determine whether the proxy server needs credentials or not:

  • No, there are no credentials necessary: Do not use credentials for proxy connections.
  • Yes, the proxy server requires credentials: Define credentials (username and password) below.

User

This setting is only visible if you enable Yes, the proxy server requires credentials above. Enter a username for proxy authentication. Enter a string.

Password

This setting is only visible if you enable Yes, the proxy server requires credentials above. Enter a password for proxy authentication. Enter a string.

Probe Connection Settings

Probe Connections IPs

Define how PRTG handles incoming connections from probes:

  • Local Probe only, 127.0.0.1 (PRTG will not be accessible for remote probes): The PRTG core server only accepts local probe connections. You cannot use remote probes with this setting enabled. This is the default setting in PRTG on premises.
  • All IPs available on this computer: The PRTG server always accepts incoming connections from remote probes, no matter on which IP address of the core server they come in.

icon-prtg-on-demandThis is the default setting in PRTG hosted by Paessler.

  • Specify IPs: The PRTG server accepts incoming connections from remote probes only on the selected IP address(es) of the core server. In the list, select the IP addresses by adding a check mark in front of the desired IPs.

icon-i-roundYou can also change this setting in the PRTG Administration Tool on Core Server System.

icon-i-round-redIf you change this setting, PRTG needs to restart the core server to apply your changes. After clicking Save, a dialog box appears that asks you to confirm the required core server restart. Click OK to trigger the restart. During the restart, all the users of the PRTG web interface, of PRTG Desktop, or of PRTG Apps for Mobile Network Monitoring are disconnected and reconnected.

icon-prtg-on-demandThis option is not available in PRTG hosted by Paessler.

Access Keys

Enter a list of access keys, one per line. Every (remote) probe that wants to connect to this PRTG installation has to use one of these keys.

icon-book-arrowsFor more information on how to set this key for a probe, see section PRTG Administration Tool.

Allow IPs

Enter a list of remote probe IPs or Domain Name System (DNS) names that are accepted when connecting to this PRTG installation. Provide one IP address or DNS name per line. The local probe (127.0.0.1) is always allowed automatically. PRTG checks the list of allowed addresses before the list of denied addresses.

  • [Empty]: An empty field does not allow any remote probes (only the local probe). Enter IP addresses or DNS names to allow remote probe connections.
    icon-i-roundWe recommend that you use IP addresses rather than DNS names, because DNS name resolution may be cached.
  • any: Enter the word any to automatically allow all remote probe connections.

icon-prtg-on-demandThis is the default setting in PRTG hosted by Paessler.
icon-i-roundWe recommend that you only use this option in intranets in PRTG on premises.

icon-i-roundIf the IP address of your remote probe changes regularly (for example, because of an internet provider assigning IP addresses dynamically), enter the potential IP range for this remote probe or use the any option.

icon-i-roundYou can use the PRTG syntax for IP address ranges here. For more information, see section Define IP Ranges.

Deny IPs

Enter a list of remote probe IPs or DNS names that are not accepted when connecting to this PRTG installation. Provide one IP address or DNS name per line. This is useful to explicitly deny connections from certain remote probes you do not want to include in your setup anymore (for example, for a certain time).

Access to IP addresses or DNS names you allowed above are denied if you enter them here. This is useful to allow access to an IP range in the field above, but deny access to a single IP address. You can use the PRTG syntax for IP address ranges here (see section Define IP Ranges).

icon-i-roundWe recommend that you use IP addresses rather than DNS names, because DNS name resolution may be cached.

Deny GIDs

Enter a list of global IDs (GID), one GID per line. The access to matching GIDs is denied. If you remove a remote probe from the device tree or if you deny a remote probe after installation, its GID is automatically entered here. This specific remote probe is not able to connect anymore. Denying GIDs is more precise than denying IPs, where other remote probes at the same location could be excluded, too.

icon-i-roundA GID is the ID that PRTG Network Monitor attributes to every device that you include in your monitoring.

Connection Security

Specify the security level that is used for connections from and to the PRTG core server:

  • High security (TLS 1.2): The web server only accepts high security connections from probes.
  • Default security (TLS 1.1, TLS 1.2) (recommended): The web server additionally accepts TLS 1.1–secured connections from probes.
  • Weakened security (SSL V3, TLS 1.0, TLS 1.1, TLS 1.2): If you have probes that do not support high or default security connections because you updated from an older PRTG version, you can choose this security level to connect and update older probes. After updating, we recommend that you use the default or high security setting.

icon-i-round-redIf you change this setting, PRTG needs to restart the core server to apply your changes. After clicking Save, a dialog box appears that asks you to confirm the required core server restart. Click OK to trigger the restart. During the restart, all the users of the PRTG web interface, of PRTG Desktop, or of PRTG Apps for Mobile Network Monitoring are disconnected and reconnected.

icon-prtg-on-demandThis option is not available in PRTG hosted by Paessler.

Mini Probes

Define if you want to allow Mini Probe connections to your PRTG server. If you want to use Mini Probes, you need to set up your PRTG web server to accept connections from Mini Probes here and choose the secure HTTPS server option in the web server settings. Choose from:

  • No Mini Probes: Mini Probes cannot connect to your PRTG web server. You are not able to monitor with Mini Probes if you choose this option.
  • Allow Mini Probes to connect to the web server: Mini Probes can connect to your PRTG web server and use the defined TCP port for the web server for this purpose. The default port for Secure Sockets Layer (SSL) connections is 443.
  • Allow Mini Probes to connect to an extra port: Mini Probes can connect to your PRTG web server via a specific port. This is useful if you do not want to have your whole PRTG web server reachable from other networks all the time only because of Mini Probes.
    icon-i-roundSSL must be active on the Mini Probe port.

icon-book-bulbSee section Mini Probe API for the full Mini Probe documentation. See also the Knowledge Base: Where can I find PRTG Mini Probes which are ready to use?

icon-i-round-redIf you change this setting, PRTG needs to restart the core server to apply your changes. After clicking Save, a dialog box appears that asks you to confirm the required core server restart. Click OK to trigger the restart. During the restart, all the users of the PRTG web interface, of PRTG Desktop, or of PRTG Apps for Mobile Network Monitoring are disconnected and reconnected.

icon-prtg-on-demandThis option is not available in PRTG hosted by Paessler.

Mini Probe Port

This field is only visible if you enable Allow Mini Probes to connect to an extra port above. Enter the number of the port that you want to use for Mini Probe connections. Ensure that SSL is available on this port.

icon-i-round-redIf you change this setting, PRTG needs to restart the core server to apply your changes. After clicking Save, a dialog box appears that asks you to confirm the required core server restart. Click OK to trigger the restart. During the restart, all the users of the PRTG web interface, of PRTG Desktop, or of PRTG Apps for Mobile Network Monitoring are disconnected and reconnected.

icon-prtg-on-demandThis option is not available in PRTG hosted by Paessler.

Active Directory Integration

icon-prtg-on-demandThis option is not available in PRTG hosted by Paessler.

Domain Name

To use the Active Directory Integration, enter the name of your local domain. Enter a string or leave the field empty.

icon-i-round-redPRTG does not support trusted domains or AD subdomains. For more important notes about AD integration, see section Active Directory Integration—Notes and Limitations.

Access Type

Define which user account PRTG uses to configure Active Directory (AD) access:

  • Use the PRTG core service account (usually LOCAL SYSTEM): Use the same Windows user account configured for the PRTG core server service. In a default installation, this is the "local system" Windows user account. If this account does not have the right to query all groups of your Active Directory, do not use this option.
  • Use explicit credentials: Define a user account that PRTG uses to authenticate against the Active Directory. This should be a user account with full access to all of your Active Directory groups.

PRTG uses this account to query the AD for existing groups.

Access User

This field is only visible if you enable Use explicit credentials above. Enter the Windows user account name that PRTG uses to authenticate for Active Directory configuration.

Access Password

This field is only visible if you enable Use explicit credentials above. Enter the password for the Windows user account that PRTG uses to authenticate for Active Directory configuration.

Historic Data Purging: Define for how many days historic data remains accessible

Data purging enables you to automatically delete unnecessary data to free up disk space and improve system performance. You can define different time spans for several kinds of data. Select here for how many days historic data remains accessible.

icon-book-arrowsFor further information on storage locations, see section Data Storage.

icon-prtg-on-demandThis option is not available in PRTG hosted by Paessler.

icon-prtg-on-demandPRTG hosted by Paessler purges historic data using the default purging limits of PRTG on premises (see the table below). You cannot modify historic data purging limits in PRTG hosted by Paessler.

Logfile Records

Define how long records in the system logfile Log Database.db are kept. Enter a value in days. All entries older than this value are deleted from the logfile automatically. This also affects the content of the Logs tab of monitoring objects like sensors. Keep this value as low as possible to enhance system performance.

icon-i-roundThe default value is 30 days.

Web Server Log Records

PRTG creates one web server logfile every day. Define how many web server logfiles are kept. Enter a value in days. All web server logfiles older than this value are deleted automatically.

icon-i-roundThe default value is 30 days.

Historic Sensor Data

Define for how many days historic sensor data is kept for all sensors. It is used to create reports of monitoring data. Enter a value in days.

Depending on the used intervals and the number of sensors in your setup, the file containing this data can become large. For smaller installations (up to 500 sensors) a value of 365 is usually fine.

icon-i-round-redHistoric sensor data is the basis for reports on monitoring data. If you decrease this value, less historic monitoring data is available.

icon-i-roundThe default value is 365 days.

icon-i-roundThe maximum value is 9999 days.

Toplist Records

Define how long toplist records for Flow and Packet Sniffer sensors are kept. Enter a value in days. We recommend that you use 30 days here.

icon-i-roundOld toplist data is deleted automatically as soon as a limit of 2 GB is reached. The oldest data is deleted from the database first.

icon-i-roundThe default value is 30 days.

Closed Tickets

Define how long tickets that are in status closed are kept. Enter a value in days.

icon-i-roundThe default value is 365 days.

Reports

Reports generated in PDF format are stored on disk for later reference. Define the maximum age for these reports. Enter a value in days. All reports that are older than this value are deleted automatically.

icon-i-roundThe default value is 365 days.

Configuration Auto-Backups

PRTG creates one backup of your configuration every day. Define the maximum age for these backups. Enter a value in days. All configuration backup files that are older than this value are deleted automatically.

icon-i-roundThe default value is 365 days.

Screenshots of HTTP Full Web Page Sensor

Define how long the screenshots of the HTTP Full Web Page sensor (PhantomJS browser engine) are kept. Enter a value in days. PRTG deletes older screenshots with every sensor scan.

icon-i-roundThe default value is 10 days.

icon-i-round-redSave your settings. If you change tabs or use the main menu, all changes to the settings are lost.

Remote Probe Setup

For more information about setting up remote probes, see section Multiple Probes and Remote Probes.

More

PRTG Manual:

Knowledge Base: Where can I find PRTG Mini Probes which are ready to use?

Setup—Topics

Others

There are some settings that you must make in the PRTG Administration Tool, available as native Windows application. For more details, see the sections: