fix: lower PAGE_VIEW_CAPTURE_FAILED severity from WARNING to INFO - #111
Merged
Merged
Conversation
Page-view capture/clear failures were reported at WARNING severity, which produced high log volume. Move them to INFO so they're rate limited under the INFO bucket and no longer crowd the WARNING channel.
rmi22186
approved these changes
Aug 5, 2026
github-actions Bot
pushed a commit
that referenced
this pull request
Aug 5, 2026
## [1.30.2](v1.30.1...v1.30.2) (2026-08-05) ### Bug Fixes * lower PAGE_VIEW_CAPTURE_FAILED severity from WARNING to INFO ([#111](#111)) ([12e179d](12e179d))
Collaborator
|
🎉 This PR is included in version 1.30.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The page-view capture feature (#109) reports capture/clear failures at
WARNINGseverity. In practice these fire often enough that WARNING log volume has climbed. This lowers all threePAGE_VIEW_CAPTURE_FAILEDreports toINFO, which is rate limited under its own per-severity bucket and no longer crowds the WARNING channel that genuine warnings rely on.Changes
capturePageView— localStorage write failure (quota/storage disabled) →INFOINFOprocesson session end — clear failure →INFOINFOThe reporting path, endpoint, and error handling are otherwise unchanged — only the
severityfield differs. Failures are still surfaced (never thrown out of the forwarder) and still bounded by the reporting service's per-severity rate limiter (RATE_LIMIT_PER_SEVERITY = 10).Verification