PRTG Manual: Core & Probes
On the Core & Probes tab, you can define settings for the PRTG core server as well as for probe connections if you use remote probes or mini probes.
If you cannot save changes to Core & Probes settings because you get an Error (Bad Request) with the message Active Directory Domain not accessible, make sure that you provide the correct access type for your domain in section Active Directory Integration. For example, change Use the PRTG core server service account (usually Local System) to Use explicit credentials and provide correct credentials for the domain. PRTG automatically sets the access type to Use the PRTG core server service account (usually Local System) by default, so you might need to change this.
If 15 minutes (900) seconds have passed since your last credential-based login and you open a setup page from a different setup page, PRTG asks you to enter your credentials again for security reasons. A dialog box appears. Enter your Login Name and Password and click OK to continue.
This 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:
This option is not available in PRTG Hosted Monitor.
Setting |
Description |
---|---|
Proxy Server Handling |
Define if you want to use PRTG with a direct internet connection or if a proxy is necessary. Choose between: ▪Do not use a proxy server (default): Do not use a proxy. Use this setting if a direct internet connection to the PRTG core server system is available. ▪Use a proxy server: Define proxy settings below. Use this setting if a proxy is mandatory in your network.
|
Server |
This setting is only visible if you select Use a proxy server 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 select Use a proxy server above. Enter the port number of the proxy server that you use for outbound connections. Enter an integer. |
Proxy Authentication |
This setting is only visible if you select Use a proxy server above. Determine whether the proxy server needs credentials or not: ▪Do not use authentication: Do not use credentials for proxy connections. ▪User name and password: Define credentials (user name and password) below. Use this setting if the proxy server requires credentials. |
User Name |
This setting is only visible if you select User name and password above. Enter a user name for proxy authentication. Enter a string. |
Password |
This setting is only visible if you select User name and password above. Enter a password for proxy authentication. Enter a string. |
Setting |
Description |
---|---|
Define how the PRTG core server handles incoming connections from probes: ▪Local probe only, 127.0.0.1 (PRTG is not accessible for remote probes): Only accept local probe connections. The PRTG core server does not allow the use of remote probes.
▪All IP addresses available on this computer: Accept incoming connections from remote probes, no matter on which IP address of the PRTG core server they come in.
▪Specify IP addresses: Accept incoming connections from remote probes only on the selected IP address(es) of the PRTG core server. In the list, select the IP addresses by enabling a check box in front of the desired IP addresses.
|
|
Access Keys |
Enter a list of access keys for remote probe connections. Enter one access key per line.
|
Enter a list of remote probe IP addresses or Domain Name System (DNS) names that you want to allow to connect to the PRTG core server. Enter one IP address or DNS name per line. ▪[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. ▪any: Enter the word any to automatically allow all remote probe connections.
|
|
Enter a list of remote probe IP addresses or DNS names that you do not want to allow to connect to the PRTG core server. Enter one IP address or DNS name per line.
|
|
Deny GIDs |
Enter a list of global IDs (GID) Enter one GID per line. PRTG denies access to matching GIDs.
|
Connection Security |
Specify the security level that the PRTG web server accepts for connections to and from the PRTG core server: ▪High security (TLS 1.2): Only accept high security connections from probes. ▪Default security (TLS 1.1, TLS 1.2) (recommended): Additionally accept TLS 1.1-secured connections from probes. ▪Weakened security (SSLv3, TLS 1.0, TLS 1.1, TLS 1.2): Additionally accept TLS 1.0-secured and SSLv3-secured connections from probes.
|
Mini Probes |
Define if you want to allow mini probe connections to the PRTG core server. Choose from: ▪Do not allow mini probes: Mini probes cannot connect to the PRTG web server. You are not able to monitor with mini probes if you choose this option. ▪Allow mini probes to connect to the PRTG web server: Mini probes can connect to the PRTG web server and use the defined TCP port for the web server for this purpose. The default port for secure connections is 443. ▪Allow mini probes to connect to an extra port: Mini probes can connect to the PRTG web server via a specific port. Use this if you do not want the whole PRTG web server to be reachable from other networks all the time only because of mini probes.
|
Mini Probe Port |
This setting is only visible if you select Allow mini probes to connect to an extra port above. Enter the number of the port for mini probe connections. Ensure that SSL is available on this port.
|
This option is not available in PRTG Hosted Monitor.
Setting |
Description |
---|---|
Domain Name |
To use the Azure Active Directory (Azure AD) integration, enter the name of your local domain. Enter a string or leave the field empty.
|
Domain Access |
Define how PRTG performs AD queries: ▪Use domain name: Use the entry in the Domain Name field above. ▪Specify domain controllers: Use specific domain controllers. Specify the domain controllers below. |
Primary Domain Controller |
This setting is only visible if you select Specify domain controllers above. Enter the DNS name of the primary domain controller. |
Backup Domain Controller (optional) |
This setting is only visible if you select Specify domain controllers above. Optionally enter the DNS name of the backup domain controller or leave the field empty. |
LDAP Connection Security |
Define if you want to use a Secure Sockets Layer (SSL)/Transport Layer Security (TLS) secured connection to the LDAP server: ▪Use LDAP without connection security: Do not use an SSL/TLS-secured connection. ▪Use LDAP over SSL: Use an SSL/TLS-secured connection. |
Access Type |
Define which user account PRTG uses to configure Active Directory (AD) access: ▪Use the PRTG core server 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 available groups. |
User Name |
This setting is only visible if you select Use explicit credentials above. Enter the Windows user account name that PRTG uses to authenticate for Active Directory configuration. |
Password |
This setting is only visible if you select Use explicit credentials above. Enter the password for the Windows user account that PRTG uses to authenticate for Active Directory configuration. |
Data purging enables you to automatically delete unnecessary data to free up disk space and to improve system performance. You can define different time spans for several kinds of data.
For more information on storage locations, see section Data Storage.
PRTG Hosted Monitor purges historic data using the default purging limits of PRTG Network Monitor. You cannot modify historic data purging limits in PRTG Hosted Monitor.
Setting |
Description |
---|---|
Log File Records |
Define how long PRTG keeps records in the system log file Log Database.db. Enter a value in days. PRTG automatically deletes all entries that are older than this value. This also affects the content of the Logs tab of monitoring objects like sensors.
|
PRTG Web Server Log Records |
PRTG creates one PRTG web server log file every day. Define how many PRTG web server log files to keep. Enter a value in days. PRTG automatically deletes all PRTG web server log files that older than this value.
|
Historic Sensor Data |
Define for how long PRTG keeps historic sensor data for all sensors. Enter a value in days.
|
Toplist Records |
Define for how long PRTG keeps toplist records for Flow (NetFlow, jFlow, sFlow, IPFIX) and Packet Sniffer sensors. Enter a value in days. We recommend that you use 30 days here.
|
Closed Tickets |
Define for how long PRTG keeps tickets that are in the Closed status. Enter a value in days.
|
Reports |
Define the maximum age for PDF reports. Enter a value in days. PRTG automatically deletes all reports that are older than this value.
|
Configuration Auto-Backups |
Define the maximum age for daily configuration backups. Enter a value in days. PRTG automatically deletes all configuration backup files that are older than this value.
|
Screenshots of HTTP Full Web Page Sensor |
Define for how long PRTG keeps the screenshots of the HTTP Full Web Page sensor (PhantomJS browser engine). Enter a value in days. PRTG automatically deletes screenshots that are older than this value with every sensor scan.
|
Save your settings. If you change tabs or use the main menu without saving, all changes to the settings are lost.
KNOWLEDGE BASE
Where can I find PRTG mini probes which are ready to use?
▪https://kb.paessler.com/en/topic/61215
There are some settings that you must make in the PRTG Administration Tool. For more details, see the sections: