Cairn
NousResearch/hermes-agent

Telemetry shared-metrics packaging with catalog-drifted or out-of-contract rows

Cluster 133017 · hermes cli. Data as of

Nothing open on GitHub. Fix merged in #137668 on 13 Oct 2026. Check it covers your case.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #137668. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #137668. That is separate from the fix event.
Still open
Nothing open on GitHub.

The members appear to concern shared-metrics telemetry packaging when stored rows contain values that no longer match the current catalog, such as a counter row outside the contract. One item proposes re-bucketing such rows instead of aborting the package, one reports that a single bad row aborts packaging for all metrics in the period, and a third references related issue and salvage numbers about telemetry after an update drops a value.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #137668 Telemetry keeps sending after an update drops a value old rows still hold (#133017, salvage #133069)

    merged to main

    files: hermes_cli/observability/shared_metrics.py, hermes_cli/observability/shared_metrics_drift.py, tests/hermes_cli/test_relay_shared_metrics.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #133069 fix(telemetry): re-bucket catalog-drifted shared-metric rows instead of aborting the package · merged via another change → 0438ca2, fb3f20a, #137668
Closed issues · 1
  • Closed#133017[Bug]: one out-of-contract counter row aborts shared-metrics packaging for every metric in the period
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
hermes cli
Merged PRs
#137668
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
13 Oct 2026

For your agent

The same facts, typed.

cluster/133017.json
cluster/133017.md