Monitoring report

monsys reports on itself every week. The report appears on Monday after midnight (Belgian time) under Reports, Monitoring report and covers the previous week. An owner or admin can create a report on the last 7 days at any time.

What is in it

• Systems: how many there are and how many are fully monitored (all eight setup steps).
• Availability per server: the share of five minute slots with a heartbeat, and the longest silence.
• Problems: opened, resolved, resolved by themselves, still open at the end, critical, and the median time to acknowledge and to resolve.
• Blind spots: every missing setup step, every part without fresh data and every archived server, by name.

Verify

The report is signed with Ed25519 over its canonical form (RFC 8785), with the hub key. The dashboard shows whether the signature is valid. To verify offline with the public key from https://api.monsys.ai/api/v1/keys:

pip install jcs pynacl
python3 - report.json <<'PY'
import base64, json, sys, jcs, urllib.request, nacl.signing
doc = json.load(open(sys.argv[1])); sig = doc.pop("signature")
key = json.load(urllib.request.urlopen("https://api.monsys.ai/api/v1/keys"))
nacl.signing.VerifyKey(bytes.fromhex(key["public_key_hex"])).verify(jcs.canonicalize(doc), base64.b64decode(sig["value"]))
print("valid, key", sig["key_id"])
PY

If a single character of the report changes, the signature no longer matches.