The latest hermes-memory-installer update brings a focused capability for teams already running memory-critical workloads: native SLO rollup and an accompanying Grafana dashboard. This isn’t about generic monitoring—it’s about moving from raw metrics to actionable compliance data, directly from the installer’s resource management layer. The feature targets engineers who need to track memory SLIs, define SLOs, and react to burn rates without cobbling together custom PromQL rules and dashboard panels.
The core addition is slo.rollup, a sub-system that precomputes key SLO metrics from memory usage, latency, and error signals exposed by the Hermes runtime. Instead of polling raw time series for every dashboard load, the rollup aggregates into compliance windows (7d, 30d, custom) and stores the results in a dedicated Prometheus SLO metric namespace. This drastically reduces query overhead for both dashboards and alerting pipelines.
Under the hood, the rollup uses Prometheus recording rules defined in a configuration file auto-deployed by the installer. Each SLO window creates a recording rule that calculates the ratio of good events (e.g., successful memory allocation under 100ms) over total events. For instance, a 30-day SLO for p99 latency is computed as:
