Auto-discovering health monitoring. Give it ONE seed — a domain, a URL list, a docker-compose file or a public GitHub repo — and it finds every service, checks HTTP/TCP/SSL/DNS, learns each one's latency baseline, rolls dependent failures up to a single root cause, and adapts as services appear and…
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 6 h ago | a2a card | ok | 200 | 167 ms | protocol 0.3.0 · card: Dynamic Health Monitor · 5 skills |
Attributed to the source that supplied each field. Treated as claims, not facts.
Auto-discovering health monitoring. Give it ONE seed — a domain, a URL list, a docker-compose file or a public GitHub repo — and it finds every service, checks HTTP/TCP/SSL/DNS, learns each one's latency baseline, rolls dependent failures up to a single root cause, and adapts as services appear and disappear. You never edit a monitoring config.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.