ablative docs
↑↓ move↵ openesc close
Stack Notebook ablative.com.au

Monitoring

Read health, session, usage and receipt evidence and follow changes through signals.

Open .md

Observe a run

Start from the exact session returned by the start operation. Read its recorded transport, machine and profile version. Follow calls and usage under that same agent and session rather than identifying a process from a similar display name.

Follow changes

The installed API includes a generation-based change read and grant-change streams. Read their query and stream contract before subscribing. Resume from the last supplied generation or revision; repeatedly fetching a complete list is not a substitute for consuming the change signal.

Limits and goals

A configured budget says what is intended. Its reading says what was measured. A crossing receipt says what action was requested or completed. Read these separately before claiming that a notice, compaction or stop occurred.

Reconcile uncertainty

Control and launch records have state and reconciliation operations. A client losing a reply must read that record before issuing another command. An absent receipt is unproven work, not a successful operation.

The route inventory is in HTTP operations.

Lys 0.3.1