Dashboard analytics performance and indexing improvements

NousResearch/hermes-agent · cluster 18511 · agent

Data as of

Nothing open on GitHub. Fix merged in #77627. Check it covers your case.

The short answer

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

These items address slowdowns in the dashboard analytics tab on larger databases, involving skipping full InsightsEngine processing on the usage API endpoint and adding indexes to assistant tool-call rows to speed up Insights queries.

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.

  • #77627 perf(insights): partial index for assistant tool-call scans + read-only fallback (salvage #67350)

    merged to main

    files: agent/insights.py, hermes_state_common.py, tests/agent/test_insights.py, tests/test_hermes_state.py

  • #77689 perf(dashboard): focused usage breakdown instead of full InsightsEngine (#38941 salvage)

    merged to main

    files: agent/insights.py, hermes_cli/web_server.py, tests/agent/test_insights.py, tests/hermes_cli/test_web_server.py

3 PRs closed without merging

From the close comments: superseded by another PR 2 · PR volume cleanup 1

  • #18642 perf(analytics): skip full InsightsEngine on dashboard /api/analytics/usage (#18511) · PR volume cleanup
  • #38941 perf(dashboard): skip full InsightsEngine on /api/analytics/usage (#18511) · superseded by another PR → #77689
  • #67350 perf(state): index assistant tool-call rows for Insights queries (#67341) · superseded by another PR → #77627
Closed issues · 2
  • Closed#18511Dashboard analytics tab blocks for seconds on larger session DBs
  • Closed#67341perf(state): index assistant tool-call rows for Insights queries
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.26: 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
agent
Merged PRs
#77627, #77689
Closed issues
2
Attempts
3 PRs closed without merging
Fix link checked
3 Aug 2026

For your agent

The same facts, typed.