Monitoring and security checks

Halon can now look at your systems without anyone asking. Everything lives on the new Monitoring page under Halon. See Monitoring and security.

Scheduled checks. Add a check for disk space, certificates, error budget, cost, or something else you describe in your own words, and run it every day or every week at the hour you choose. Each run reads your connected tools, works out the trend over days or weeks, and says the day something becomes a problem. Run now starts one at once.

Said once, to the right team. Each problem is posted once in the channel of the team that owns it, marked Worth knowing, Needs doing within weeks or Needs doing now, and again only if it gets worse. A problem with no owner, such as your cloud bill, goes to the monitoring channel you choose. What Halon raised lists every problem with when it was last said.

Cost. A cost check reads spend from AWS, Azure, DigitalOcean, PlanetScale, Vercel, Northflank, GitHub, Trigger.dev and Cloudflare, against the months before, with what grew.

Leaked secrets. When GitHub's secret scanning finds a secret in a connected repository, Halon works out what it reaches, reads what was done with it and proposes how to revoke and replace it, in the owning team's channel. Every change it proposes waits for a person.

Every member sees the page, and changing checks needs the Monitoring permission. Agents read what Halon raised with list_notices over MCP.