Skip to content

Reduce Hermes Sentry noise for expected operational failures - #67

Merged
owens1127 merged 1 commit into
mainfrom
fix-sentry-hermes-operational-noise
Jun 23, 2026
Merged

Reduce Hermes Sentry noise for expected operational failures#67
owens1127 merged 1 commit into
mainfrom
fix-sentry-hermes-operational-noise

Conversation

@owens1127

Copy link
Copy Markdown
Contributor

Summary

  • Fixes SERVICES-1T: autoscale/scale-in delivery channel closure no longer reports channel_closed to Sentry
  • Fixes SERVICES-28: unretryable Discord webhook 404s log at Warn (destination deactivation already handles these)
  • Fixes SERVICES-1Q / SERVICES-21: max-retry exhaustion from Cloudflare, timeouts, connection errors, and 5xx upstream logs at Warn instead of Error

Deploy

ssh raidhub
cd /RaidHub/Services && git pull origin main
export PATH=/usr/local/go/bin:$PATH
make hermes
sudo systemctl restart hermes

Test plan

  • go build ./apps/hermes/...
  • CI green
  • After deploy: confirm Sentry volume drops for SERVICES-1Q/1T/28 over 24h

Fixes SERVICES-1T, SERVICES-28, SERVICES-1Q

Made with Cursor

Downgrade autoscale channel closure, unretryable webhooks, and upstream retry exhaustion (Cloudflare/timeouts) from Error to Warn.

Co-authored-by: Cursor <cursoragent@cursor.com>
@owens1127
owens1127 merged commit 2266368 into main Jun 23, 2026
2 checks passed
@owens1127
owens1127 deleted the fix-sentry-hermes-operational-noise branch June 23, 2026 23:59
owens1127 added a commit that referenced this pull request Jun 24, 2026
#70)

Reverts #67/#68 Error→Warn and Sentry filtering — real errors stay Error and report to Sentry.
Re-resolve activity hash from raw PGCR in StorePGCR so missed-PGCR cron and stale queue messages use referenceId.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant