Skip to content

feat: retain local delivery timing samples - #80359

Open
lipton-agent-hermes wants to merge 1 commit into
NousResearch:mainfrom
lipton-agent-hermes:feat/local-delivery-timing-upstream
Open

feat: retain local delivery timing samples#80359
lipton-agent-hermes wants to merge 1 commit into
NousResearch:mainfrom
lipton-agent-hermes:feat/local-delivery-timing-upstream

Conversation

@lipton-agent-hermes

Copy link
Copy Markdown

Summary

  • retain exact local-only task and model-call timing samples in the existing private metrics store
  • expose local count/p50/p90 summaries
  • prune timing samples under the existing 30-day retention policy
  • index percentile reads by metric and duration

Privacy and safety

  • no prompts, responses, source code, raw IDs, tool arguments/results, or credentials are stored
  • shared/exported metric payloads are unchanged
  • timing-store errors are caught so task/model completion remains fail-open
  • this does not enable telemetry or restart any gateway

Proof

  • uv run --extra dev pytest -q tests/hermes_cli/test_relay_shared_metrics.py tests/hermes_cli/test_relay_shared_metrics_runtime.py
  • 153 passed
  • git diff --check
  • fresh privacy/correctness review; retention/index finding reconciled with regression coverage

@alt-glitch alt-glitch added type/feature New feature or request P3 Low — cosmetic, nice to have comp/cli CLI entry point, hermes_cli/, setup wizard telemetry Touches outbound telemetry, usage attribution, or analytics — needs opt-in gating before merge labels Aug 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp/cli CLI entry point, hermes_cli/, setup wizard P3 Low — cosmetic, nice to have telemetry Touches outbound telemetry, usage attribution, or analytics — needs opt-in gating before merge type/feature New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants