<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: System Administration—Monitoring
To open system administration, select Setup | System Administration from the main menu. Click on the tabs to change the different settings.
System Administration Bar
You can define the following aspects of your PRTG system setup:
- System Administration—User Interface
- System Administration—Monitoring
- System Administration—Notification Delivery
- System Administration—Core & Probes
- System Administration—Cluster
- System Administration—User Accounts
- System Administration—User Groups
- System Administration—Administrative Tools
In the monitoring settings you can define global values regarding scanning intervals, unusual and similar sensors detection, auto-discovery, and uptime threshold.
Note: If you open this system administration page from another administration page and 15 minutes (900 seconds) have passed since your last credential based login, you have to provide your credentials again for security reasons. A dialog box will appear. Enter your Login Name and Password for PRTG in the corresponding fields and click on the Login button. You can continue with your task immediately.
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 available as described. When using a cluster installation, failover nodes are read-only by default.
Scanning Intervals |
|
---|---|
Available Intervals |
Define the intervals available in the drop down list of every object's settings. In the text field, enter one value in each line. Use s, m, h, and d for defining seconds, minutes, hours, and days. By default, there are the following scanning intervals defined: 30s: 30 seconds 1m: 1 minute 5m: 5 minutes 10m: 10 minutes 15m: 15 minutes 30m: 30 minutes 1h: 1 hour 4h: 4 hours 6h: 6 hours 12h: 12 hours 1d: 1 day Note: We recommend that you do not use intervals shorter than 10 seconds to prevent system overload. Intervals below 10 seconds are not officially supported! The maximum supported scanning interval is 10 days. You can also define specific points in time to indicate when PRTG executes scanning actions. Enter up to 50 concrete UTC points in time according to the formula @ UTC hh:mm, hh:mm Note: Your local time may be different from the UTC time! For more information on how to set specific points in time as a scanning time for sensors, see the More section below. |
Unusual Detection |
|
---|---|
The unusual detection can set sensors to an Unusual status when there are values that are untypical for the time span in which they are measured. PRTG compares the current average values to the historic monitoring results for this purpose. If the current values show a big difference to the values that are normally retrieved by a sensor, this sensor will indicate this with the unusual status. You can define the granularity of the detection here (this means, how big the difference must be to cause an unusual status). If you disable the unusual detection (both settings to Never), sensors will never show an unusual status. Note: You can enable and disable unusual detection for specific devices, entire groups, and probes in the respective Object Settings. |
|
Show Unusual When |
Define when a sensor shows the unusual status, comparing the weekday. If you enable the detection here, the average of the values which were measured on the day before is compared to the average of the same weekday in previous weeks. Choose between:
For example, consider a traffic sensor that usually measures 100 MB average traffic on a weekday. If you choose the first option, it would show an unusual status if the average from the day before is below 80 MB or above 120 MB. |
Show Unusual When |
Define when a sensor shows the unusual status, comparing the hour-of-day. If you enable the detection here, the average of the values which were measured in the hour before is compared to the average of the same hour on the same weekday in previous weeks. Choose between:
Consider a traffic sensor that usually measures 10 MB average traffic within an hour. If you choose the first option, it would show an unusual status if the average from the hour before is below 8 MB or above 12 MB. |
Logging |
Define if unusual events will be written to the log file. Choose between:
|
Similar Sensors Detection |
|
---|---|
Similar sensors detection enables PRTG to analyze sensor data for similarities. The detection will run in the background with low priority. The recommended setting for similar sensors detection is to let PRTG automatically decide how many channels will be analyzed. However, you can also override this setting. Note: When similar sensors analysis is turned off or you have exceeded 1,000 sensors and have chosen the automatic analysis depth option, the similar sensors entry will not be shown in the main menu bar. |
|
Analysis Depth |
Define the number of channels PRTG will analyze to detect similarities between sensors or turn the analysis off. Choose between:
|
Recommended Sensors Detection |
|
---|---|
With the sensor recommendation engine, you can automatically analyze the devices which you add to PRTG for useful but missing sensors. PRTG can show you sensor types that give you a much more detailed picture about your network when you monitor the respective devices with them. The analysis runs with low priority in background when you add a new device, the last analysis has been 30 days ago, or you click Recommend Now in the context menu of a device or on a device overview tab. When the analysis is finished for a device, suggested sensor types appear in the Recommended Sensors table list on the device overview tab. You can add them directly to the device with the Add Sensors button. Note: To recommend SNMP sensors for a device, the detection engine uses the SNMP version that you define in the Credentials for SNMP Devices section of the device settings. Note: The detection engine cannot run at the same time as Auto-Discovery. PRTG gives auto-discovery a higher priority, for example, when you add a new device, and queues the sensor recommendation in this case. Note: The detection engine only checks if a certain sensor type currently exists on a device and recommends to add this sensor if not found. It does not check if there already existed a sensor of this type on the device and was deleted previously! Because of this, sensor types appear in the "Recommended Sensors" list again if they are categorized as useful for the according device when you have deleted all sensors of this type. |
|
Detection Engine |
Define if you want PRTG to analyze your devices to recommend useful sensor types. Choose between:
|
Auto-Discovery |
|
---|---|
Run Discovery at |
Define the time when PRTG automatically runs an Auto-Discovery in your network if you configured a daily or weekly Discovery Schedule in the auto-discovery group settings. Choose a full hour between 0:00 and 23:00. We recommend you to choose a time when there is little user activity in your network, because auto-discoveries can produce a certain amount of load. |
Uptime Threshold |
|
---|---|
Desired Minimum Uptime |
Define which uptime in percent PRTG regards as 100 percent. This setting affects the colors shown next to the sensor icons in reports. Select one of the predefined values between 90 % and 99.999 %. |
Click Save to store your settings. If you change tabs or use the main menu, all changes to the settings will be lost!
Knowledge Base: How can I speed up PRTG—especially for large installations?
Knowledge Base: How and where does PRTG store its data?
Knowledge Base: Can I set a sensor to run at a specific time?
There are some settings that you have to make in the PRTG Administration Tool, available as native Windows application. For more details, please see the sections: |
---|
Keywords: