Sixty containers, zero monitoring agents installed

Monitoring usually starts with a rollout: install the agent on every host, configure it, keep it patched, repeat for each new machine.

On Hoody there's nothing to roll out. Every container's terminal service already exposes the answers as endpoints: /api/v1/system/resources for CPU, memory, and disk; /api/v1/system/processes?sort=cpu&limit=10 for what's eating them; /api/v1/system/ports for what's listening. Your dashboard curls sixty containers on a loop and renders the fleet. A new container is monitorable the second it exists, because the endpoints came with it.

Nothing installed, nothing to upgrade, nothing that breaks when the agent vendor changes their pricing.

The container ships with its own monitoring API.