Skip to content

Metrics: keep chrome essentials on histogram failure, gate PID walk on deadline#313

Draft
sjmiller609 wants to merge 1 commit into
mainfrom
hypeship/metrics-review-followups
Draft

Metrics: keep chrome essentials on histogram failure, gate PID walk on deadline#313
sjmiller609 wants to merge 1 commit into
mainfrom
hypeship/metrics-review-followups

Conversation

@sjmiller609

Copy link
Copy Markdown
Contributor

Summary

Follow-ups to two review findings that landed after #309 merged:

  • A UMA histogram fetch failure now logs and skips only the histogram family instead of returning an error — which, under the handler's discard-on-error policy, was throwing away the already-gathered kernel_chromium_up / info / pages samples and hiding the browser-up signal exactly when the browser was struggling.
  • The system collector checks the scrape deadline before starting the /proc PID walk, so an expired scrape doesn't begin new work while holding the scrape lock.

Test plan

  • Updated TestChromeCollectorHistogramFailure: essentials survive, UMA family absent
  • go vet + full unit suite pass

🤖 Generated with Claude Code

A UMA histogram fetch failure now logs and skips only the histogram
family instead of discarding the whole chrome scrape — the up, info,
and pages samples survive, so browser-up alerting keeps its signal.
The system collector checks the scrape deadline before starting the
/proc PID walk.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.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