Status reporting (self-severity)

Scripts that decide for themselves whether the system is ok, warn, or crit, and POST to a severity-specific URL. Pair with a capture.severity check on the receiving object to alert at the level the script chose.

batch

Batch — report crit

Sends a self-reported crit. Use for hard failures (service down, backup didn't run, disk full). Wakes everyone subscribed to crit alerts.

batch

Batch — report ok

One-line cmd.exe POST to the /ok severity URL. Pair with a capture.severity check (and a capture.freshness check on the same object, so silence also alerts).

batch

Batch — report warn

Sends a self-reported warn. Use when something is degraded but still working (high disk usage, slow response, partial outage). Body's `summary` field is shown in the alert.

powershell

PowerShell — report any severity

Single PowerShell script that takes the severity as a parameter, so you can call it from a wrapper that decides ok/warn/crit based on your own logic. Usage: .\status.ps1 -Severity ok .\status.ps1 -Severity warn -Summary 'Disk 92% full' .\status.ps1 -Severity crit -Summary 'Backup script failed'