hermes-agent/agent/monitoring
Victor Kyriazakos 6de6e36dbe fix(monitoring): surface cron snapshot failures at WARNING (content-free)
The cron health snapshot failure path logged only at DEBUG, so a cron
telemetry regression would silently drop all hermes.cron.* metrics while
gateway health metrics kept flowing. Promote to WARNING with the
exception *type* name only (no message text, preserving the no-raw-error
contract); keep the traceback on DEBUG.

(cherry picked from commit 1c9a3e737b7c57fa9886bc927f1623753a9a811b)
2026-07-25 01:54:31 +00:00
..
__init__.py
cron_health.py fix(monitoring): correct cron operational signals 2026-07-24 18:54:46 +00:00
emitter.py fix(monitoring): drain terminal lifecycle events 2026-07-24 18:54:45 +00:00
events.py feat(monitoring): add cron operational telemetry 2026-07-24 18:54:46 +00:00
gateway_health.py fix(monitoring): enrich gateway diagnostic scope 2026-07-24 18:54:46 +00:00
gateway_health_export.py fix(monitoring): surface cron snapshot failures at WARNING (content-free) 2026-07-25 01:54:31 +00:00
otlp_exporter.py feat(monitoring): add cron operational telemetry 2026-07-24 18:54:46 +00:00
policy.py fix(monitoring): address review — persist install_id, drop dead config, single redaction path 2026-07-24 18:54:45 +00:00
redaction.py fix(monitoring): enrich gateway diagnostic scope 2026-07-24 18:54:46 +00:00