History¶
History is the first tab under Governance in the device sidebar. Its page, Config History, is one timeline, newest first, that holds two kinds of entry:
- every configuration version the device has had,
- every change to the device itself, such as a rename or an uplink switch.
Who sees it¶
Governance (History, Logs and Diagnostics) appears in the sidebar only for people who may read the device's activity record: an Organization Owner, a Support or Support Admin holder on the organization or the device, and platform administrators. An Organization Member or a Device Owner does not see it.
Filtering the timeline¶
- All, Configuration or Updates picks which entries to show. Updates shows the device changes.
- Author narrows the timeline to one person. It appears when more than one person has made changes.
- Export (.csv) downloads the timeline.
Configuration versions¶
Each saved configuration is a version. The entry shows the version number, its status, its hash, who created it and when it was applied. The version the device is running is marked ACTIVE.
| Status | Meaning |
|---|---|
| Draft | Saved, not applied |
| Queued | Waiting to be sent to the device |
| Pending | Sent, waiting for the device to report back |
| Awaiting Confirm | Running on the device, inside the confirm window |
| Confirmed | Confirmed. This is the committed configuration |
| Rolled Back | Not confirmed in time, or the device failed, so it went back to the previous version |
| Failed | The device could not apply it |
Click a version to open it. You see Applied, By and Note, then Changes vs v{prev}: for each section, what was added, changed and removed. The sections are Interfaces, Firewall rules, NAT rules, Routes, Network objects, Services, Schedules and Web filtering. Below that, Configuration shows the full configuration.
The first version shows First version — nothing before it to compare. A version identical to the one before shows No configuration changes from the previous version.
What the confirm window actually does¶
When you apply a configuration, the portal shows Config applied — {seconds}s to confirm or rollback. You have 60 seconds to click Confirm. If nobody confirms, the device goes back to the previous configuration and the portal shows Config v{version} was not confirmed and has been rolled back.
- The timer runs on the device. A device that loses contact as soon as the configuration lands still rolls back on its own.
- You cannot confirm a change that cut off your access. The rollback then restores what worked.
- The whole configuration is restored: firewall, uplink failover, DHCP, DNS resolver, interfaces and static routes. The services that use them are reloaded.
Trying a risky change
Apply it and do not confirm. You get 60 seconds to see the effect, and the device restores itself even if you can no longer reach it.
Applying interrupts traffic briefly
DHCP and uplink failover restart when a configuration lands, which causes a short outage on the uplink in use.
Rolling back¶
- Open the version you want to return to.
- Click Rollback to v{version}. The button shows Rolling back....
The rollback creates a new version from the old one and applies it. History is kept, and the rollback appears as the newest entry. It goes through the same 60-second confirm window as any other change.
The button is not offered on the active version, on drafts, or on pending versions.
Device changes¶
These entries record changes to the device rather than to its configuration. Each shows the change as {from} → {to}, Set to {value}, or Cleared (was {value}).
Changes made by a person:
| Entry | When |
|---|---|
| Display name changed | The device is renamed in Settings |
| Hostname changed | Its hostname changes |
| Model changed | Its hardware model changes |
| Hardware replaced | A different physical unit takes over this device |
| Assigned to organization | It leaves the holding zone for an organization |
| Returned to holding zone | It is removed from its organization |
| Release channel changed | It is moved to another agent release channel |
Changes the device reports itself. Their author is shown as the device:
| Entry | When |
|---|---|
| Internet uplink switched | Traffic moved to another uplink, for example Switched to {to} — {from_} stopped answering. See failover |
| Internet uplink health changed | An uplink became unusable ({iface} stopped carrying traffic reliably.) or usable again ({iface} is usable again.) without traffic moving |
| Agent updated | The device finished updating its agent |
| Agent update failed | An update did not complete and the device kept its previous version |
Judge a backup uplink before you need it
A backup uplink that drops and recovers moves no traffic, so it only appears here as Internet uplink health changed. A backup with several of these a day is not reliable.
These entries are dated by the device's own clock. A device that switched uplink while it was cut off reports the switch when it reconnects, with the time it happened.
Two people editing one device¶
A save sends the whole configuration. If someone else saved a newer version while you were editing, your save is refused:
this device changed while you were editing it: you started from v10 and it is now v12. Reload before saving, or your change would revert what happened in between
Nothing is written. Reload the page and make your change again.