Read a canister's overview
A canister’s Overview answers one question: is this canister fine? It puts its state, cycles, memory, traffic and recent changes on one page, for the time range you choose at the top.
The coverage line
Section titled “The coverage line”Under the canister’s name, the coverage line shows each signal and its state:
Select a signal to see what it needs, if anything, such as access for the Agent or a client in your code. What each state means.
The figures
Section titled “The figures”| Figure | Tells you |
|---|---|
| Cycles | The balance, and roughly how many days it lasts. |
| Burn | How fast it spends cycles over the range. |
| Memory | How much memory it uses, and how much its snapshots hold. |
| Query calls | Its average query traffic. |
| Availability | How often it answered its availability check. Shown once it has one. |
The panels
Section titled “The panels”- Where cycles go splits spending into compute, memory, requests and more. Switch between the range and the all-time total. It needs the Agent to control the canister.
- Memory splits memory into heap, stable memory, snapshots and the rest.
- Query traffic shows calls per minute as a heatmap.
- Traps counts the canister’s traps, with code changes marked.
- Changes lists its latest code changes and events. View all opens the Timeline.
- Details has its controllers, freezing threshold, module hash and more.
Good to know
Section titled “Good to know”- Every figure comes from the Internet Computer itself: your canister needs no code changes for any of it.
- In This browser, the overview shows the current state only. History, burn over time and traps over time come from an Agent.
- When a figure can’t be read yet, it says why: loading, no access, or not collected. It never shows zero instead.