How Monitor works
Monitor is your Agent watching your canisters for you. It reads them on a schedule, checks your alert rules, and tells you when something needs attention, even when no one has icLens open.
What it does
Section titled “What it does”- Reads every canister in the workspace: health, cycles, memory, and more if you turn it on. What Monitor reads.
- Checks your rules against what it read, such as “cycles below 5 TC”. Alert rules.
- Acts: posts to Slack or a webhook, or tops up a canister from the Reserve. Slack and webhooks.
Where to find it
Section titled “Where to find it”Open Monitor in an Agent workspace:
| Section | Shows |
|---|---|
| Overview | Whether Monitor is on, what it reads, and how often. |
| Alerts | Alerts that are firing, pending or resolved. |
| Rules | The conditions it checks. |
| Receivers | Where alerts are sent. |
| Availability | Scheduled calls that check your canisters answer. Mainnet only. |
One switch
Section titled “One switch”Start Monitor turns everything on: reads, rules, logs and availability checks. Pause Monitor stops it all. Agent setup offers to start Monitor for you.
Pausing keeps your history and firing alerts, but it ends automatic top-up authorizations. Authorize them again after you resume.
Good to know
Section titled “Good to know”- Monitor runs on the Agent’s own cycles. Reading more often, or reading more, costs more.
- Anyone in the workspace can see alerts. Changing rules and receivers needs an Admin.
- An alert shown in icLens doesn’t prove a notification arrived. Each alert shows what was sent.