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

You can download the historic monitoring data for one sensor in the Extensible Markup Language (XML) format or the comma-separated values (CSV) format using the following API calls. You can either request the results of each single monitoring request (called raw data) or you can let PRTG calculate averages of the data (for example, hourly or daily averages).

To avoid potential server overload, the number of requestable values per API call is limited by means of automatic averaging as follows:

API calls for historic data are limited to 5 requests per minute.

API Calls for Historic Data

Authentication with username and passhash (or username and password) must always be included in each PRTG API request. See section Authentication for more information.

The API calls for historic data tables look like this:

You must supply the object ID of a sensor as well as a start date/time sdate and end date/time edate.

If you use the JSON call, additionally provide the parameter usecaption=1 to get more information than just the raw data table.

API Call for Historic Graphs

Historic graphs are also available (in the PNG format):

Common Parameters for Historic Data API Calls

You can use the following parameters for the graphs and the data tables:

Historic Data Query Builder

You can also use the historic data function to manually generate and analyze historic sensor data via the PRTG web interface.

More

KNOWLEDGE BASE

How can I export historic data from the PRTG API?

• https://kb.paessler.com/en/topic/76768

How can I export raw sensor data automatically from PRTG?

• https://kb.paessler.com/en/topic/343

Application Programming Interface (API) Definition—Topics

• HTTP API
• Live Data

• Single Object Property
• Single Object Status
• Multiple Object Property or Status
• System Information

• Live Graphs
• Historic Data
• Object Manipulation
• Custom Sensors
• Custom Notifications
• Mini Probe API