Diagnostic Logs and Support Procedures

When absolute resilience fails, forensic visibility is your only recourse. StateWarden provides highly detailed telemetry and an immutable audit trail designed for rapid Root Cause Analysis (RCA).

When contacting StateWarden Enterprise Support, or when performing your own internal diagnostics, relying on vague descriptions ("the backup failed") is insufficient. You must utilize the built-in diagnostic tools.

1. The Realm Audit Log (Control Plane)

The primary source of truth for the entire infrastructure is the Realm Audit Log. This log does not contain low-level debug code; it contains a cryptographic record of actions and state changes.

• Location: Dashboard -> Realm Settings -> Audit Logs.
• What it tracks: Login events, RBAC modifications, Backup Policy executions, BMR Token generation, Quota rejections, and Vigil suppressions.
• Usage: If an Administrator asks, "Why didn't the database backup run last night?", the Audit Log will immediately reveal if Artemis rejected the task via a QUOTA_EXCEEDED event, or if a user manually executed a BACKUP_DELETE command.

2. Device-Level Logs (The Agent)

If the Control Plane dispatched the task successfully but the operation failed locally (e.g., a locked disk, a network timeout, a VSS fault), you must consult the Agent's internal logs.

StateWarden's Agent is written in Rust and utilizes a high-performance, leveled logging architecture.

Viewing Logs via the Dashboard

For standard errors, you do not need to SSH or RDP into the affected machine.

1. Navigate to the Devices view.
2. Select the affected Device to open its detailed panel.
3. Click the Logs tab. The Agent securely streams its recent local output back to the Artemis Control Plane for easy viewing.

Accessing Raw Logs Locally

For severe failures (e.g., the Agent is completely offline and cannot stream to the Dashboard), you must access the raw text files on the host machine.

• Windows: C:\ProgramData\StateWarden\logs\
• Linux (Systemd): Use journalctl -u sw-agent.service --no-pager or check /var/log/statewarden/.

3. Support Notes (CRM Integration)

In enterprise environments with dedicated support tiers, tracking the ongoing resolution of an issue requires documentation.

StateWarden includes a built-in Support Notes system attached to every Realm.

• Location: Dashboard -> Realm Settings -> Support Notes (Visible only to users with appropriate RBAC roles).
• Usage: Support engineers and Realm Administrators can append timestamped, markdown-formatted notes detailing their diagnostic steps, identified workarounds, or communication logs with StateWarden L2 Support.
• Security: These notes are strictly isolated and shielded from standard Operator roles.

4. Generating a Secure Support Bundle

If you escalate an issue to StateWarden Engineering, they will require technical context.

To prevent the accidental transmission of sensitive data (like Master Keys or proprietary configuration files) via insecure email channels, the StateWarden CLI provides a secure bundling command.

1. Open a terminal on the affected machine.
2. Execute: sw diag bundle
3. The Agent will automatically collect recent log files, network configuration state, VSS writer statuses (Windows), and basic hardware telemetry.
4. Crucially, it will sanitize the bundle, ensuring no cryptographic material or PII is included.
5. It produces a compressed .zip or .tar.gz archive ready for secure transmission to our support desk.

StateWarden: Resilience Engineered.