mirror of
https://github.com/Studio-Saelix/sencho.git
synced 2026-07-27 20:29:10 +00:00
SaelixCode
99a1cb45be
Realign the page with the current Anatomy panel tab strip and the StackActivityTimeline component: - Frame the Activity tab as a sibling of Anatomy under the right-hand panel, with files/edit actions belonging to the strip. - Expand the category guidance: list the five iconized categories and call out that other stack-scoped notifications (deploy failure, available image updates, auto-heal triggers, monitor alerts, scan findings) flow into the timeline with a generic icon. - Tighten the actor-attribution rule to match the component: omitted for events without an actor and for system-driven events. - Add the day-format example to the relative-time row. - Recapture both screenshots from a populated stack (Today + Yesterday + Earlier with three distinct icons) and an empty stack. - Convert troubleshooting blurbs to H3 for anchor links and consistency with the v1-refresh sibling pages.
73 lines
3.9 KiB
Plaintext
73 lines
3.9 KiB
Plaintext
---
|
|
title: Stack Activity
|
|
description: Per-stack event log showing deploys, restarts, config changes, and alerts, each attributed to the user or system that triggered them.
|
|
---
|
|
|
|
The **Activity** tab in the right-hand **Anatomy** panel gives you a timestamped record of everything that happened to the selected stack: deploys, restarts, starts, stops, and image updates. Each entry shows who triggered the event so you always have operational context. The `files` and `edit` actions on the same strip belong to the panel as a whole and stay available regardless of which tab is active.
|
|
|
|
<Frame>
|
|
<img src="/images/stack-activity/activity-tab-populated.png" alt="Stack Activity tab showing events grouped by Today, Yesterday, and Earlier with restart, auto-update, and image-update entries" />
|
|
</Frame>
|
|
|
|
## What you'll see
|
|
|
|
Each entry in the activity list contains:
|
|
|
|
| Field | Description |
|
|
|-------|-------------|
|
|
| **Icon** | Category of the event (deploy, restart, stop, start, image update applied) |
|
|
| **Message** | What happened (for example, `dozzle restarted`) |
|
|
| **Attributed to** | `by <username>` for user-initiated actions; omitted for events without an actor and for system-driven events such as auto-update or auto-heal |
|
|
| **Time** | Relative time since the event: `just now`, `5m ago`, `2h ago`, `3d ago` |
|
|
|
|
## Event categories
|
|
|
|
The five operational categories below have a dedicated icon. Other notification categories that scope to a stack (for example, deploy failures, available image updates, auto-heal triggers, monitor alerts, or scan findings) also flow into the timeline and render with a generic activity icon.
|
|
|
|
| Category | Icon | Example message |
|
|
|----------|------|-----------------|
|
|
| Deploy succeeded | rocket | `plex deployed` |
|
|
| Stack restarted | refresh | `dozzle restarted` |
|
|
| Stack stopped | stop | `radarr stopped` |
|
|
| Stack started | play | `radarr started` |
|
|
| Image update applied | up arrow | `Auto-update: stack "dozzle" updated with new images` |
|
|
|
|
## Day grouping
|
|
|
|
Events are grouped by day under three headers: **Today**, **Yesterday**, and **Earlier**. Within each group, events are ordered most-recent first.
|
|
|
|
## Live updates
|
|
|
|
New events stream in over the same WebSocket that powers the notification bell, so the list updates without a page refresh while the tab is open.
|
|
|
|
## Pagination
|
|
|
|
The tab loads the most recent 50 events on open. If a stack has more recorded events, a **Load more** button appears at the bottom of the list. Each click fetches the next 50 older events.
|
|
|
|
## Empty state
|
|
|
|
When a stack has no recorded operational events yet, the tab displays a heartbeat icon with the message `No activity recorded yet`.
|
|
|
|
<Frame>
|
|
<img src="/images/stack-activity/activity-tab-empty.png" alt="Stack Activity tab in its empty state with a heartbeat icon and the message 'No activity recorded yet'" />
|
|
</Frame>
|
|
|
|
## Who triggered an event
|
|
|
|
Sencho attributes every recorded event to the user who was authenticated when the action was taken. Events without an actor, and events triggered by automated processes such as auto-update polling or auto-heal, are recorded as system actions; the attribution label is omitted from their display.
|
|
|
|
## Accessing the Activity tab
|
|
|
|
1. Click any stack in the left sidebar to open it.
|
|
2. Switch to the **Activity** tab in the Anatomy panel header.
|
|
|
|
## Troubleshooting
|
|
|
|
### The Activity tab shows "No activity recorded yet"
|
|
|
|
The activity log is populated by operations performed through Sencho on this stack: deploys, restarts, starts, stops, and image updates. Trigger one of those actions and the entry appears within a few seconds.
|
|
|
|
### Operational events don't appear in the bell notification dropdown
|
|
|
|
The notification dropdown surfaces system alerts and error-level events. User-initiated operational events (start, stop, restart, deploy, update) appear exclusively in the per-stack Activity tab, keeping the global tray focused on conditions that need your attention.
|