From 2a46acc9be6089dcc631a07b9ff452230ba417cd Mon Sep 17 00:00:00 2001 From: Victor Kyriazakos Date: Fri, 24 Jul 2026 18:44:43 +0000 Subject: [PATCH] docs(monitoring): clarify bounded cron flush --- docs/observability/monitoring.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/observability/monitoring.md b/docs/observability/monitoring.md index cdec47c496e..f13ebc161b9 100644 --- a/docs/observability/monitoring.md +++ b/docs/observability/monitoring.md @@ -48,9 +48,9 @@ hermes monitoring status The OpenTelemetry SDK is an optional extra (`pip install 'hermes-agent[otlp]'`), lazy-installed on first use. When the SDK is missing or the endpoint is down, -the gateway runs unaffected: every export path is fail-open and off the hot -path (events flow through a fire-and-forget in-process emitter; a slow or -failing exporter can never block gateway code). +the gateway runs unaffected: metric collection and ordinary event export stay +off the hot path, while terminal cron events make one bounded fail-open flush +attempt of up to one second so the final state is less likely to be lost. Works identically under systemd/launchd/s6 supervision, containers, tmux, or a plain `hermes gateway run` — the exporter lives in the gateway process, so