Debug/sentry initialization #132
Open
Conversation
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
Add extensive logging to diagnose why Sentry traces aren't being collected: - Log Sentry initialization in withSentry callback (always, not just dev) - Log HTTP tracing middleware execution for every request - Enhanced /debug-sentry endpoint with full diagnostics - Log DSN presence, length, and configuration status - Log available Sentry methods and environment keys This will help identify if: 1. SENTRY_DSN environment variable is missing 2. Sentry SDK is not initializing 3. HTTP tracing middleware is not running 4. startSpan function is not available Debug logs are prefixed with [SENTRY DEBUG] for easy filtering. Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Add extensive logging to diagnose Sentry initialization issues: - Log DSN validation steps (existence, type, length) - Log all VITE_ environment variables - Log full Sentry configuration (temporarily including full DSN) - Send test message and log event ID - ALWAYS log (not just in development mode) This will help identify if VITE_SENTRY_DSN is missing or invalid.
- Use Record<string, unknown> type for safer property access - Remove unnecessary logger test code that caused type issues
Contributor
Author
|
@sentry review |
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 pull request adds comprehensive Sentry debug logging and diagnostics across both backend (
cloudflare.ts,hono/app.ts) and frontend (main.tsx) code, making it easier to verify Sentry configuration, initialization, and runtime status in all environments. Logging is now always enabled (not just in development), and diagnostic endpoints and test messages are included to confirm Sentry is working as expected.Sentry Debug Logging and Diagnostics
Backend (
cloudflare.ts,hono/app.ts):cloudflare.ts, including checks for DSN existence, length, and available environment keys. Logging now usesconsole.errorfor missing DSN and is always enabled. [1] [2]hono/app.tsto log Sentry status and span creation for every request, with warnings if Sentry is not configured./debug-sentryendpoint to provide comprehensive diagnostics, including runtime info, DSN details, available Sentry methods, environment keys, and attempts to send test errors and logs to Sentry, with robust error handling.Frontend (
main.tsx):