When the On-Premise Poller loses internet connectivity, it continues to monitor your infrastructure and holds the collected data locally until the connection is restored. This article explains how the On-Premise Poller stores data during an outage, how it syncs the backlog afterward, and what limitations apply during prolonged outages.
The On-Premise Poller continues data collection even when the network is unavailable. If the On-Premise Poller cannot reach Site24x7, the data collection (DC) is marked as a failed report, and the file is stored in the failed folder on disk instead of being discarded.
How long these files are retained depends on the device type:
Once connectivity is restored, the On-Premise Poller uploads all the failed files using separate, dedicated threads. This upload runs in parallel and doesn't interfere with ongoing data collection. The data collection file (called reports) can be a maximum of 150 KB in size and can contain data collection data for one or more monitors.
General monitor data (excluding network monitors)
The sync duration depends on how long the outage lasted and how much backlog has built up. The On-Premise Poller sends data collection files at the following rate:
| Sync frequency | One file every 30 seconds |
|---|---|
| Maximum data points per file | 50 |
| Maximum zip file size | 150 KB |
| Parallel upload threads | 10 (default) |
| Sync scalability | Up to 1,200 files per hour (10 parallel threads × 120 files per hour each) |
Network monitoring data
| Devices per file | 10 |
|---|---|
| Maximum zip file size per report | 1.5 MB |
| Upload time per file | Up to 30 seconds |
| Parallel upload threads | Five (default) |
| Sync scalability | Up to 600 files per hour |