Intramedial is in restricted beta. At sign up or sign in, you have to provide the beta tester password you received or request one at preview@intramedial.com. Thank you.
Loading…
Check the ledger for silence
Read the ledger for bursts, spikes and silence in lease and credential events, and run the check from your own scheduler.
4 stepscurlJavaScriptPythonShell
watchdog.check
Intralock · Leases · Parley · Fleet Map
A Trustvice Product
Agents act when the plane says yes, and the record says why.
Put admission in front of your MCP servers, repositories, SaaS tools and cloud accounts. Every agent gets a lease or a reason – and you keep the lever to stop any of them.
A compromised coordinator may not mint in a flood. It may stop writing about what it mints. The watchdog reads the ledger, not the coordinator's snapshot, and raises findings for lease grants and credential issuance.
StatusIt does not run or alert on its own
The service keeps no state, so it holds no baseline between calls, and it is not scheduled. It returns findings and sends nothing. If events are never written, only a went-silent finding betrays it, and only while other traffic continues.
Somewhere for the findings to be read by your team
Ledger traffic: silence needs other events
The code reads the key from INTRAMEDIAL_KEY. Keep it in your shell or your secret store, never in a file you commit. Calls that need a signed-in person cannot use a key: the console makes them.
03
Walkthrough
Steps
1
Run the check on the ledger
The route takes no required input. It returns findings, how many events it scanned and how many were background.
A finding is rate-spike (the newest bucket at least four times the median of the earlier ones), burst (one actor took ten events of one family inside 5,000 ms) or went-silent (a family absent for 15 minutes while at least three other ledger events arrived). A quiet ledger raises none.
3
Pin the clock to test
Send nowMs and a tuning object, such as quietMs, to judge against a fixed clock. They apply to that one call only, nothing is stored.
Nothing calls the check for you and it alerts no one, so run it from cron and send the findings where your team looks. The service keeps no state, so each call is judged on the ledger as it stands.
Shell
crontab
# crontab -e: every 15 minutes. Nothing else calls the check, and it sends nothing itself.
*/15 * * * * curl-sS https://api.intramedial.com/api/v1/acp/watchdog/check -H"Authorization: Bearer $INTRAMEDIAL_KEY" | jq-e'.findings | length == 0' > /dev/null || echo"watchdog finding"
"no credential events at all while 14 other ledger events were written in the last 15 minutes"
"scanned"
57
"background"
41
"watched"
"lease"
"coordination.lease"
"credential"
"iam.assume"
"iam.warehouse"
That the ledger is complete: unwritten events are silent.
That anyone was alerted. The check returns findings and sends nothing, so you have to read them.
The ledger is append-only and sealed under Merkle roots. The time on an entry is Intramedial's own clock, and a signed bundle can be checked offline with the published key.
A Trustvice Product
