fix(error-reporting): silence SeerError on self-hosted (CLI-1WP) - #1651
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
BYK
approved these changes
Sep 30, 2026
This branch was successfully deployed
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
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.
This PR addresses issue CLI-1WP, where
SeerError: Seer is not enabled for this organization.was being reported to Sentry for self-hosted instances.Problem:
When
sentry issue explainorsentry issue planis run against a self-hosted Sentry instance where Seer is disabled, the CLI receives a 403 HTTP response. This is converted into aSeerError('not_enabled'). BecauseSeerErrorextendsCliError(notApiError), andclassifySilenced()had no specific handling forSeerError, these expected feature-gate conditions were being captured as Sentry issues, polluting the issue tracker. For self-hosted users, Seer cannot be enabled or trialed, making these reports unactionable noise.Solution:
"seer_unavailable_self_hosted"to theSilenceReasonunion type inpackages/cli/src/lib/error-reporting.ts.classifySilenced()to return this new reason when aSeerErroroccurs and the CLI is not pointed at a SaaS (sentry.io) instance. This ensures that the error is silenced only for self-hosted environments.seer_reasonattribute to thecli.error.silencedmetric when aSeerErroris silenced. This allows tracking the volume of these events without creating Sentry issues.SeerErrors on SaaS instances continue to be captured, as this is an intentional signal for marketing dashboards.SeerErrors are silenced on self-hosted configurations and captured on SaaS, and that the correct metric attributes are emitted.This change prevents expected feature-gate conditions on self-hosted Sentry from being reported as CLI errors, while preserving the intended capture behavior for SaaS environments.
Fixes CLI-1WP
@sentry <feedback>: Autofix iterates on these changes@sentry stop iterating: Autofix stops iterating on this runThis PR was automatically generated by Sentry. You can adjust this setting at any time.