<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Historic Data Reports

For quick reviews of a sensor's monitoring data, use the historic data reports as an alternative to the comprehensive Reports function. You can run and view a report of the historic data for each single sensor, on demand. Additionally, you can export this sensor data as XML or CSV files to your computer for further processing with third-party applications.

There are two ways to open PRTG historic data reports: either you click the Historic Data tab on a sensor's detail page, or you choose Sensors | View Historic Data from the main menu.

Historic Data (Sensor Tab)

Probe, group, device, and sensor pages have tabs that you can use to navigate between the different options. For example, you can view your network's status, view monitoring results, or change settings.

Tabs Bar on Sensor Pages

The Historic Data tab is available for sensors only (not for probes, groups, or devices). When you open the historic data tab of a sensor, there is no sensor selection available. If you want to select a different sensor for the report, select Sensors | View Historic Data from the main menu in the PRTG web interface.

Historic Data Tab of Ping Sensor

Historic Monitoring Data (Sensors Main Menu)

When you open historic data reports via Sensors | View Historic Data in the main menu, PRTG will ask you to choose the sensor you want to create a report for with the Object Selector.

Historic Monitoring Data Settings

Settings
Sensor	This field is only visible if you open the historic data function via the main menu. Select the sensor you want to create the report for: click the reading-glass symbol to open the object selector. For more information, see section Object Selector.
Start	Specify the start date and time of the data you want to review. Use the date time picker to enter the date and time. You cannot start the report generation if monitoring data has been purged after the defined start date. Please set the start for the report to a date where data is available.
End	Specify the end date and time of the data you want to review. Use the date time picker to enter the date and time.
Quick Range	In this section, you can use several buttons for a faster selection of start and end dates. Click any of these links to change the Start and End values above. Choose between: 1 Day, 2 Days, 7 Days, or 14 Days: Set the date range to the respective day(s). The current time of the current day is the end date. Today, Yesterday, Last Week (Mo-Su), Last Week (Su-Sa), Last Month, 2 Months, 6 Months, 12 Months: Set the date range to the last matching period. It starts at 00:00 and ends at 00:00 of the particularly following day.
Average Interval	With this option, you can activate and configure averaging. Select an interval for which PRTG will calculate the average value. You can choose between No Interval (no averaging is performed and only raw data displayed), a few seconds, minutes, hours, or a whole day (24 Hours). A shorter interval results in a more detailed report for this sensor. The best settings for you may vary, depending on the scanning interval of the sensor, the selected date period, and the intended use for the report. It might be useful to try different settings and compare what the results look like. See the section Automatic Averaging below.
Channels in Graph	Select the channels that you want to include in the graph of the report. You can select or deselect individual channels with the respective check boxes, and select or deselect all channels with the buttons Show all or Hide all. PRTG will only show the data of selected channels in the graph of the report. The report table will always show the data of all channels.
Cluster Node	This field is only visible if the sensor is running on a cluster probe. Select the cluster node's data that PRTG will include in the report. Choose between: All nodes: Include the data of all cluster nodes in the report. [Several specific nodes]: Use a specific node's data for the report. The nodes you see are specific to your setup.
File Format	Select the output format for the report. Choose between: HTML web page: Display the result directly as an HTML web page. This is also a good option to check results before exporting to another file format. XML file: Export the data as Extensible Markup Language (XML) file. Usually, your browser shows a download dialog when you use this option. CSV file: Export the data as Comma Separated Values (CSV) file, for example, for import into Microsoft Excel. Usually, your browser shows a download dialog when you use this option.

Include Percentiles
Percentile Results	Define if you want to include an additional percentile calculation of your data in the report. Choose between: Do not show percentiles: PRTG does not use a percentile formula to calculate your monitoring results. It will show only the standard values. Show percentiles: PRTG adds a column to the result data tables that shows percentiles for every sensor channel. Percentiles are not available for all report templates. If a template does not support percentiles, they will simply not show up in the report, even if you enable this setting. Likewise, percentiles are not available in a cluster setup if you choose the option All Nodes in the Cluster Node setting in the sensor section above.
Percentile Type	This setting is only visible if you select Show percentiles above. Enter the percentile type you want PRTG to use for the calculation. If you choose, for example, to calculate the 95th percentile, enter "95" here and 5 % of peak values will be discarded. Please enter an integer value.
Percentile Average Interval	This setting is only visible if you select Show percentiles above. Enter a value to define the averaging interval on which PRTG bases the percentile calculation. The default value is 300 seconds (5 minutes). This means that PRTG takes 5 minute averages as basic values for the percentile calculation. Please enter an integer value.
Percentile Mode	This setting is only visible if you select Show percentiles above. Choose the mode for percentile calculation: Discrete: PRTG takes discrete values to calculate percentile results. Continuous: PRTG interpolates between discrete values and bases the calculation on interpolated values.

Click Start to generate a historic data report.

You cannot start the report generation if monitoring data has been purged after the defined start date. Please set the start for the report to a date where data is available.

Remarks for Reports

Any sensor graph in your report will only show channels that are enabled via the Show in graphs option in the Sensor Channel Settings.
Reports show statistics for uptime (Up and Down in percent) and requests (Good and Failed in percent). Values between 5% and 95%, as well as 100% and 0%, are rounded to whole numbers without decimal places. Other values are shown with 3 decimal places.
Due to rounding, the statistics in section Sensor Status History of the report might differ in a few seconds from the values in section Uptime Stats.
Data reporting is limited to 5 requests per minute.
Reports cannot show uptime or downtime data for the Sensor Factory Sensor.
Create reports that include an appropriate amount of data. Reports may not work as expected if too many sensors with short scanning intervals have to be processed. Adjust your report size and time span that the report covers if necessary.

Automatic Averaging

For performance reasons, PRTG automatically averages monitoring data when calculating data for large time spans. Data is then averaged regardless of the selected average interval.

Time Span in Report	Minimum Level of Detail (Average Interval)
Up to 40 days	Any
40 to 500 days	60 minutes/1 hour or larger

Reports for time spans of more than 500 days are not possible. If you enter a longer time span, it will automatically be shortened to 365 days.

Under certain circumstances, the resulting report may contain a time span that differs from the defined start and end date because of internal averaging processes. When averages are greater than 1 hour and they do not equal 24 hours and they are combined with certain time spans, it might happen that resulting datapoints are asynchronous to the time spans. Please especially consider this behavior when you use API calls to generate reports.