Skip to content
Sutra

Features

What Sutra does today, and what is planned but not yet built.

Implemented

  • Server inventory

    Implemented

    Servers list with health, and a per-server detail page with checks and configuration.

  • Agent health

    Implemented

    Agents page showing status, version, last heartbeat and last error; a missing heartbeat raises an incident.

  • Host CPU, memory and storage

    Implemented

    Reported by the agent, with thresholds and a disk-full forecast.

  • systemd units

    Implemented

    Services and timers are inventoried and checked; stock OS units are ignored by default.

  • Docker inventory and stats

    Implemented

    Containers, images, networks and volumes, plus per-container stats.

  • PM2 processes

    Implemented

    PM2 processes are monitored per user when the agent has host access.

  • Website and SSL checks

    Implemented

    HTTP and certificate-expiry probes run by the worker.

  • Incidents

    Implemented

    Open, acknowledged and resolved states, escalation, reports and post-mortems.

  • Notifications

    Implemented

    Delivery through Microsoft Teams, SMTP email and Power Automate, with a delivery log.

  • Maintenance windows

    Implemented

    Scheduled windows that suppress alerts, with a suppression log.

  • Public status page

    Implemented

    Available without login at /status.

  • TV mode

    Implemented

    A wall display at /tv, with revocable read-only kiosk keys.

  • Role-based access

    Implemented

    Admin and viewer roles; routes check a named permission.

  • Audit log

    Implemented

    Append-only record of state-changing actions.

  • Logs on request

    Implemented

    An admin can request logs from a server through its agent.

  • Saved views

    Implemented

    Save and reuse list filters.

  • Docker network inventory and AWS network metrics

    Implemented

    Docker network names and drivers are inventoried, and AWS EC2 NetworkIn/NetworkOut are read from CloudWatch.

Planned or unverified

  • Multi-factor authentication (MFA)

    Planned

    Designed in docs/SECURITY.md (TOTP and recovery codes) but not implemented.

  • Host network throughput metrics

    Planned

    No code collecting per-host network traffic from the agent was found; treat as unverified and not available.

Setup steps are on the documentation page; security controls are described on the security page.