How to store
the PRTG monitoring data
in 3 steps


1. The PRTG database


Monitoring data usually consist of very small amounts of data that occur at regular intervals.

Our tests have shown that a classical database is not so well suited for an efficient storage of this type of data.

Therefore, we have developed our own database, which stores data in a flat file format and is optimized for monitoring data.

Your benefits:



Our database is much faster than other databases. Therefore, we are able to analyze and show historic data near real-time.

Network load

The PRTG database server is integrated into the core server. No data transfer through the network to another installation is needed.

Configuration and maintenance

No extra configuration or maintenance is necessary for our integrated database. Updates are deployed automatically with the usual PRTG updates.

Easy backup

You can simply back up the database by copying the data files.


The database is included in all PRTG licenses. No database license (e.g. SQL) is required.

Data export

In case you need your data for other applications or statistics, you can export monitoring data from PRTG at any time via the integrated API.


2. What is stored where?

General monitoring data: PRTG database
Core installation: Program directory
Monitoring configuration, monitoring data, logs, reports, etc.: Data folder
License key, admin login, IP settings, etc.: Registry


For more detailed information see our Knowledge Base.




3. How much storage space will I need in the long run?


The required long-term storage space depends on various factors.



As a rule of thumb:

You need about 200 KB of disk space per sensor per day (for sensors with 60 second scanning interval).


Disk space per sensor per day: 200 KB

Number of sensors in your PRTG installation: 1,300

Sensor data stored for: 365 days

Storage footprint: about 95 GB


This exemplary calculation applies to standard sensors. Specific sensors such as xFlow or Packet Sniffer can produce larger amounts of data. Also, the exact amount depends on the kind of data that is produced as well as the number of sensor channels.

Further Information:

This third party content uses Performance cookies. Change your Cookie Settings or

load anyways

*This will leave your Cookie Settings unchanged.