Timeline
A canister’s Timeline puts everything that happened to it on one time axis: code and settings changes, alerts, logs and live calls. Use it to answer “what changed around the time this started?”.
Read these lanes as text
Protocol, Agent, Monitor, public-network, and device evidence keep separate provenance while sharing a time axis. Only explicit relationship identifiers support causal links.
- Protocol, 12:02: Status changed
- Agent, 12:03: Observation retained
- Monitor, 12:04: Event opened
- Public, 12:06: Proposal nearby
- Device, 12:08: Operator receipt
Narrow it down
Section titled “Narrow it down”Choose All, or focus on Changes, Logs or Calls. Older events load as you scroll. Pick a range at the top, such as the last 24 hours.
Select an event to see its details and where it came from, then follow it to the right place: the code change, the alert, the snapshot.
What it contains
Section titled “What it contains”| Kind | From |
|---|---|
| Code, settings, cycles and snapshot changes | The Internet Computer and your Agent |
| Alerts | Monitor rules in your Agent |
| Logs | Collected by your Agent, or read live in this browser |
| Live calls | Watched from the network’s edge while the page is open |
Good to know
Section titled “Good to know”- Two events at the same time aren’t necessarily related. Use them as leads.
- Some times are exact; some say observed by, meaning the change happened before the Agent noticed it.
- In This browser, Timeline shows public changes, logs you can read, and live calls on demand. Full history needs an Agent.