PRTG sync
What the scheduled jobs last did. Nothing on this page triggers anything — see PRTG import to apply a new configuration.
Configuration
- Last checked
- never — config arrives by upload
- Needs a look
- nothing
| State | Rows | Means |
|---|---|---|
| new | 0 | in PRTG, not here yet — apply an import to bring it in |
| drifted | 0 | PRTG changed a field this deployment has not locked |
| locked | 0 | changed on both sides; your local value is being kept |
| missing | 0 | gone from PRTG, still here |
| skipped | 0 | could not be placed at all — see the server logs |
History sync
- Last run
- 2026-08-13 20:00 SAST
- Buckets written
- 4,362
The last history sync failed — see the server logs.
Backfill
- PRTG probes
- 1,455
- Still deepening
- 0
- Finished with PRTG's past
- 1,455 — asked further back and found nothing, repeatedly
- Not yet started
- 0
- History requested back to
- 2024-07-13
What is stored
- Span
- 2024-07-13 to 2026-08-13
- By granularity
- day 261,900, hour 905,009
- By origin
- prtg 1,166,909
- Raw samples
- 0
Shared history store
- Container
- prtg-history
- Schema version
- 2
Blobs are not counted here: enumerating the container is an unbounded call, and this page must not hang when storage is slow.
API sunset check
- Last checked
- never
- Compatibility shim
- unknown