PRTG Manual: System Administration—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, ensure 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 you use PRTG on premises and open the system administration page from a different 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.
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.
This option is not available in PRTG hosted by Paessler.
Setting |
Description |
---|---|
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:
|
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:
|
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. |
Setting |
Description |
---|---|
Probe Connections IPs |
Define how PRTG handles incoming connections from probes:
|
Access Keys |
Enter a list of access keys for remote probe connections. Enter one access key per line. Every remote probe that wants to connect to this PRTG installation has to use one of these keys.
|
Allow IPs |
Enter a list of remote probe IPs or Domain Name System (DNS) names that are accepted when connecting to this PRTG core server. Enter 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.
|
Deny IPs |
Enter a list of remote probe IPs or DNS names that are not accepted when connecting to this PRTG core server. Enter one IP address or DNS name per line. You can use this to explicitly deny connections from remote probes that you do not want to include in your setup either at all or for a certain time. Access to IP addresses or DNS names that you enter in Allow IPs is denied if you enter them here. You can use this to allow access to an IP range in Allow IPs, but to deny access to a single IP address from this IP range here. You can use the PRTG syntax for IP address ranges here (see section Define IP Ranges).
|
Deny GIDs |
Enter a list of global IDs (GID) Enter one GID per line. PRTG denies access to matching GIDs. 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. The remote probe is no longer able to connect. Denying GIDs is more precise than denying IPs, where other remote probes at the same location could be excluded, too.
|
Connection Security |
Specify the security level for connections to and from the PRTG core server:
|
Mini Probes |
Define if you want to allow mini probe connections to your PRTG core server. If you want to use mini probes, you need to configure the PRTG web server to accept connections from mini probes here and choose the secure HTTPS server option in the web server settings. Choose from:
|
Mini Probe Port |
This setting is only visible if you enable 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 by Paessler.
Setting |
Description |
---|---|
Domain Name |
To use the Active Directory integration, enter the name of your local domain. Enter a string or leave the field empty.
|
Domain Access |
Define how PRTG performs Active Directory queries:
|
Primary Domain Controller |
This setting is only visible if you enable Specify domain controllers above. Enter the DNS name of the primary domain controller. |
Backup Domain Controller (optional) |
This setting is only visible if you enable 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:
|
Access Type |
Define which user account PRTG uses to configure Active Directory (AD) access:
PRTG uses this account to query the AD for available groups. |
Access User |
This setting 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 setting 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. |
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.
For more information on storage locations, see section Data Storage.
This option is not available in PRTG hosted by Paessler.
PRTG 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.
Setting |
Description |
---|---|
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.
|
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.
|
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.
|
Toplist Records |
Define how long toplist records for xFlow (NetFlow, jFlow, sFlow, IPFIX) and Packet Sniffer sensors are kept. Enter a value in days. We recommend that you use 30 days here.
|
Closed Tickets |
Define how long tickets that are in status closed are kept. Enter a value in 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.
|
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.
|
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.
|
Save your settings. If you change tabs or use the main menu without saving, all changes to the settings are lost.
For more information about setting up remote probes, see section Add Remote Probe.
KNOWLEDGE BASE
Where can I find PRTG Mini Probes which are ready to use?
- Account Settings
- System Administration
- User Interface
- Monitoring
- Notification Delivery
- Core & Probes
- User Accounts
- User Groups
- Administrative Tools
- Cluster
- PRTG Status
- License Information
- Auto-Update
- Optional Downloads
- Help and Support Center
- Contact Support
There are some settings that you must make in the PRTG Administration Tool. For more details, see the sections: