Browse documentation
Data and retention
Settings → Data & Retention shows what JOATOS is storing, how that sits against your plan, and lets you keep less of it.
What it shows
- Storage by category and by table — where your data actually is.
- Your plan's storage and retention limits, with current usage against them.
- Recalculate — usage figures come from a periodic snapshot, so this forces a fresh count.
Retention overrides
Each class of data is kept for a period set by your plan. You can override that per class to keep less. Clearing an override returns that class to the plan default.
Shortening retention frees storage but discards history permanently. Lengthening it is bounded by the plan.
The collection log level
The same page carries a dial that decides how much collection logging is stored at all:
| Level | Stores |
|---|---|
| Everything | Every poll, successful or not |
| Warnings & errors | (default) Problems only |
| Errors only | Failures only |
| Off | Nothing |
The default means successful polls are not recorded. If a device's log looks empty while collection is clearly working, this is why — not a fault.
Two things follow from that. The level is applied as logs are written, so raising it only affects events from that moment on; nothing that was filtered out can be recovered. And the setting is organisation-wide, so turning it up to debug one device turns it up for everything.
Notes & tips
- Turn the level to Everything while diagnosing a collection problem, then turn it back. Leaving it up is the quickest way to fill your storage allowance.
- Check this page before assuming you need a bigger plan — a retention override on your noisiest data class is often enough.