Add resilient upload queue and client health
This commit is contained in:
@@ -46,6 +46,24 @@ automation read access. Set it to `true` for a device to begin the five-minute
|
||||
burst scans; clear it to stop them. The normal daily scan continues regardless
|
||||
of the checkbox.
|
||||
|
||||
## Upload Reliability And Client Health
|
||||
|
||||
If the upload endpoint is temporarily unavailable, the client stores up to 100
|
||||
signed report payloads locally under `C:\ProgramData\OCSentinel\upload-queue`.
|
||||
The next scheduled run sends queued payloads before its new report. The local
|
||||
health state is stored under `C:\ProgramData\OCSentinel\state`.
|
||||
|
||||
Create these additional device custom fields in NinjaOne and allow automation
|
||||
write access:
|
||||
|
||||
| Field name | Type | Purpose |
|
||||
| --- | --- | --- |
|
||||
| `ocsentineluploadstatus` | Text | `ok`, `queued`, or `unknown` upload state |
|
||||
| `ocsentinelqueuedreports` | Integer | Reports waiting for delivery |
|
||||
| `ocsentinellastuploadutc` | Date/Time | Last successful upload time |
|
||||
| `ocsentinellasterror` | Text | Last upload error, if any |
|
||||
| `ocsentinelclientversion` | Text | Installed client version |
|
||||
|
||||
## NinjaOne Tasks
|
||||
|
||||
Create a PowerShell script in NinjaOne named `OCSentinel - Installieren oder aktualisieren`.
|
||||
|
||||
Reference in New Issue
Block a user