Malachi.
View Source
Real-time operational and security metrics kept in ETS (atomic update_counter), plus a
periodically-sampled system snapshot and its recent history.
The increment_*/record_* functions bump counters on the hot path (fast, lock-free), rate-limit and
connection-limit blocks, auth failures and account lockouts, audit events, dashboard-auth outcomes, and
TLS handshakes; get_system_metrics/0 reads the live BEAM snapshot
(memory, processes, io) folded together with those counters, and get_history/1 returns the recent
snapshots. A counter is created on first touch, so callers never need to initialize one.
Summary
Functions
Returns a specification to start this module under a supervisor.
The recent per-second history samples for the last seconds (default 60).
A snapshot of system-wide metrics (memory, processes, connections, auth) for the dashboard.
Increment account lockout counter.
Increment account lockout blocked attempt counter.
Increment audit event counter by event type.
Increment connection limit blocked counter.
Increment dashboard authentication blocked (rate limited) counter.
Increment dashboard authentication failure counter.
Increment dashboard authentication success counter.
Increment failed authentication attempt counter.
Increment rate limit blocked counter for specific action.
Increment TLS handshake failure counter.
Increment TLS handshake success counter.
Records an authentication attempt with result (:ok / :error).
Records count records consumed (from the consume telemetry event).
Records a segment that failed checksum verification, by reason (:bad_crc, :bad_magic,
:incomplete). Non-zero means data at rest is damaged somewhere on this node, which is otherwise
a silent condition: a damaged copy serves short reads without any error.
Records count records and bytes value bytes produced (from the produce telemetry event).
Records a quorum replication with result (:ok / :no_quorum).
Records one integrity scrub pass: how many segments it verified, repaired, and could not repair. A verified total that stops advancing is how an operator sees that the scrub itself has stopped, which the failure counters alone cannot show (they stay at zero both when all is well and when nothing is checking). The unrepairable total is the one that calls for a human: it counts damage the cluster could not heal by itself, which on a single node is every finding there is.
Record the negotiated TLS version for a connection.
Starts the metrics server (owns the ETS counter table).
Functions
Returns a specification to start this module under a supervisor.
See Supervisor.
The recent per-second history samples for the last seconds (default 60).
A snapshot of system-wide metrics (memory, processes, connections, auth) for the dashboard.
Increment account lockout counter.
Increment account lockout blocked attempt counter.
Increment audit event counter by event type.
Increment connection limit blocked counter.
Increment dashboard authentication blocked (rate limited) counter.
Increment dashboard authentication failure counter.
Increment dashboard authentication success counter.
Increment failed authentication attempt counter.
Increment rate limit blocked counter for specific action.
Increment TLS handshake failure counter.
Increment TLS handshake success counter.
Records an authentication attempt with result (:ok / :error).
Records count records consumed (from the consume telemetry event).
Records a segment that failed checksum verification, by reason (:bad_crc, :bad_magic,
:incomplete). Non-zero means data at rest is damaged somewhere on this node, which is otherwise
a silent condition: a damaged copy serves short reads without any error.
Records count records and bytes value bytes produced (from the produce telemetry event).
Records a quorum replication with result (:ok / :no_quorum).
Records one integrity scrub pass: how many segments it verified, repaired, and could not repair. A verified total that stops advancing is how an operator sees that the scrub itself has stopped, which the failure counters alone cannot show (they stay at zero both when all is well and when nothing is checking). The unrepairable total is the one that calls for a human: it counts damage the cluster could not heal by itself, which on a single node is every finding there is.
Record the negotiated TLS version for a connection.
Starts the metrics server (owns the ETS counter table).