SYS.DOCS // DOCS
Cluster Settings: Events
Use Cluster Settings → Events to troubleshoot and audit cluster operations such as provisioning, updates, and deletions.
This page is not the same as Diagnostics:
- Events tracks Edka lifecycle and operation telemetry.
- Diagnostics tracks Kubernetes warning events, K3s signals, and pod-level failures inside the cluster.
Live vs history mode
Section titled “Live vs history mode”The Events page automatically switches behavior based on cluster status:
- LIVE mode when status is
pending,creating,updating, ordeleting. - HISTORY mode when no operation is in progress.
Unlike other settings pages, Events remains available during active operations so you can monitor progress in real time.
Event telemetry
Section titled “Event telemetry”The Event Telemetry summary shows:
- Total events
- Success events
- Error events
Event console
Section titled “Event console”The Event Console groups records into operation runs (for example provisioning or update runs) and shows:
- Operation label and sequence number.
- Events count and quick success/error counters.
- Started and latest event timestamps.
- Per-event messages and metadata.
Per-event metadata can include:
- Timestamp
- Operation
- Progress percentage
- Component
- Step
- Source
Filtering and refresh
Section titled “Filtering and refresh”You can filter events by:
- Operation: All, Provisioning, Updates, Deletions, Other
- Outcome: All, Success, Errors, Processing
You can also:
- Refresh manually at any time.
- Clear filters to return to the full timeline.
Empty and error states
Section titled “Empty and error states”The page provides explicit states for:
- No events recorded yet
- No events matching current filters
- Temporary load errors (with retry via refresh)