Resource → History

The History tab merges recorded activity for this resource into a single, day-grouped, newest-first timeline. Six event streams are interleaved into one feed:

• Config changes — every saved configuration snapshot, with chips listing the snap elements that actually changed since the previous version.
• Sessions — active, completed, and failed interactive or file-transfer sessions, with their status and duration. Interactive sessions use a terminal icon; File transfer sessions use an open-folder icon and offer file-operation review after they end.
• Health transitions — moments when the resource’s overall status flipped (e.g. healthy → degraded). Chips name the metrics that were failing at that tick.
• Compliance changes — moments when a compliance rule’s verdict flipped for this resource, with one chip per changed rule, colored by its new status.
• Configuration pushes — every push made from the Configure tab or by automation, with the stack, status, and who (or what) triggered it.
• AI agent runs — Quick Assist and background runs associated with the resource, including configuration and session analyses. Entries and their output dialog match Review → Agents, including running, completed, and failed runs.

The same tab is available on every resource and every location detail page. At location scope it includes resources at that location and its sub-locations, plus AI runs directly associated with those locations, within your access scope. Report-generated AI runs remain in Review → Agents and are excluded from History.

For health changes across the fleet, use Review → Health. Health entries share the same arrows, severity colors, and actions in both views.

For compliance changes across the fleet, use Review → Compliance. Compliance entries share the same grouping, rule chips and colors in all three views.

What you can do

• Browse a unified narrative of the resource over time.
• Open the config captured at any historical point.
• Diff a config version against the one before it.
• Request an AI analysis of a config version — as a diff against the previous version, or a description of the very first one.
• Replay a recorded session.
• Drill into a health transition with the metric history chart.
• Open the record of a configuration push — what was sent and what the device answered.

Row anatomy

Each row shows a timestamp, the event type (with its icon), and event-specific fields. Per-row content gates on which streams have data — a resource with no snapshots simply has no config rows.

Stream	Per-row buttons
Config	Eye — view the captured config. Diff — compare against the previous version (hidden on the first version). Robot — request an AI analysis (shown when an analysis agent exists for the resource type and you may use Quick Assist).
Session	Play — open the replay for ended terminal sessions; graphical sessions (RDP/VNC/Web) get a screen icon opening the graphical replay instead. Ended terminal rows also carry a robot button for an AI Session Analysis. File transfer rows use an open-folder button to review file operations, without requiring a terminal recording. Replay and operation review remain unavailable while a session is active.
Health	Chart — open the metric history modal centered on the transition. A robot button asks the AI for a Resource Summary of what is going on.
Compliance	Eye — view check details at the event time (requires compliance-read access). When several rules changed together, select a rule in the modal. Chips name the changed rules and their new status.
Config push	Eye — View push record: a dialog showing the rendered content (as sent) and the resource output.
AI agent run	Eye — View output: the same output dialog as Review → Agents. The row shows the agent, status color, trigger, duration, and token usage when available.

The list scrolls infinitely — older entries load as you scroll down.

Active sessions show an Active badge. Refreshing updates the same entry when the session completes or fails; its original timeline position is preserved. Unstarted reservations are not included. For live observation and termination controls, use Review → Sessions.

Common tasks

Compare two consecutive config versions

1. Find the entry whose changes you want to review.
2. Click the diff button. (Missing button → no previous version exists.)
3. The diff modal lists the changed elements down the left side; select one to see its added and removed lines on the right.

Replay a session

1. Click the play button on a Session row.
2. The session replay opens in a new view. See Sessions for the player controls.

Inspect a health transition

1. Click the chart button on a Health row.
2. The metric history chart opens centered on the transition time, showing how each metric behaved before and after.

Get an AI summary of a config change

1. Click the robot button on a Config row.
2. An AI agent runs with the before/after configuration as context — or, on the very first captured version, with just that version, producing a description instead of a diff summary.
3. A panel opens with a plain-language summary of what was added, changed, or removed.

Only resource types with a registered config-analysis agent show this button.

Config changes across the estate

History is the per-resource timeline. For the estate-wide, config-only view with cross-resource filters, use the Review → Changes page.

Permissions

• View the timeline and AI run output: app.resources.read, within your location scope.
• View compliance events: app.fact_policies.execute, within its location scope.
• Open a captured config or a diff: app.changelog.read.
• Open a session replay: app.session.read.
• Open a push record: app.configure.execute, within its location scope.
• Request AI analysis: app.ai.execute.