Overview
Telemetry covers the collection, transmission, and analysis of data from a running system, used to monitor performance, diagnose issues, and guide operational decisions. In Stalwart, telemetry provides the signals administrators rely on to understand system behaviour, track performance, and validate reliability and security.
Events
Events are specific occurrences within the server that are recorded for monitoring, auditing, and troubleshooting. They cover every aspect of operation, from authentication attempts to message delivery. Stalwart emits hundreds of distinct events, each identified by a hierarchical name such as auth.success or delivery.delivered.
Tracing & Logging
5 items
Metrics
3 items
Webhooks
Webhooks deliver real-time notifications about server events by posting to an HTTP endpoint of the operator's choice. They let external systems react to activity in the server without polling; typical uses include recording deliveries into an analytics pipeline, flagging authentication anomalies to a SIEM, or triggering automated workflows on message ingestion.
Alerts
Alerts notify administrators when a server metric, or a combination of metrics, crosses a defined threshold. The condition is evaluated continuously against the live metrics stream, and when it holds, a notification is emitted. Notifications can be delivered as an in-server event (which a webhook can forward downstream) or as an email message.
Live Telemetry
Live telemetry exposes an HTTP endpoint that streams structured logs, traces, and metrics to the client in real time. The stream is delivered using Server-Sent Events (SSE), so any HTTP client capable of consuming an event stream can subscribe. The feature is suited to live diagnostics, short-lived performance investigations, and dashboards that need a continuous update path.
History
Telemetry history retains selected event spans (for example, incoming messages and completed deliveries) and periodic metric samples in a dedicated database, so that past activity can be reviewed after the fact. Unlike live telemetry, which streams data to connected clients in real time, history persists the signal to storage for later query.
Management
Traces, metrics, and log entries are runtime telemetry records produced by the server and retained according to the configured telemetry history. The existing Live telemetry page covers real-time streaming, and the History page covers the backends and retention windows that persist this data. Once persisted, the records themselves are accessible as management objects through the WebUI, the CLI, and the JMAP API.