Skip to content

Conversation

@jnsdls
Copy link
Member

@jnsdls jnsdls commented Jun 21, 2025

TL;DR

Replaced Sentry Replay integration with PostHog Sentry integration in the dashboard app.

What changed?

  • Removed the Sentry Replay integration that was blocking media and masking text
  • Added PostHog Sentry integration with organization set to "thirdweb-dev" and projectId set to 6690186
  • Updated the comment to indicate the integration of Sentry with PostHog

How to test?

  1. Verify that Sentry events are properly forwarded to PostHog
  2. Check that the PostHog dashboard shows Sentry events from the thirdweb-dev organization
  3. Confirm that error tracking continues to work as expected

Why make this change?

This change integrates Sentry with PostHog to consolidate analytics and error tracking data in one platform. This will provide better correlation between user behavior and errors, improving our ability to diagnose issues and understand their impact.


PR-Codex overview

This PR focuses on integrating Sentry for error tracking and monitoring in the application, alongside existing PostHog analytics. It involves the initialization of Sentry with various configurations to filter errors and integrate with PostHog.

Detailed summary

  • Removed sentry.client.config.ts.
  • Added Sentry initialization in instrumentation-client.ts with:
    • allowUrls and denyUrls for filtering.
    • dsn for Sentry project.
    • ignoreErrors to ignore specific common errors.
    • Integration with PostHog using posthog.sentryIntegration.
    • Configuration for error sampling rates.
  • Exported onRouterTransitionStart for router navigation tracking.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@changeset-bot
Copy link

changeset-bot bot commented Jun 21, 2025

⚠️ No Changeset found

Latest commit: c09123d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link

vercel bot commented Jun 21, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
thirdweb-www ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 21, 2025 7:31pm
4 Skipped Deployments
Name Status Preview Comments Updated (UTC)
docs-v2 ⬜️ Skipped (Inspect) Jun 21, 2025 7:31pm
nebula ⬜️ Skipped (Inspect) Jun 21, 2025 7:31pm
thirdweb_playground ⬜️ Skipped (Inspect) Jun 21, 2025 7:31pm
wallet-ui ⬜️ Skipped (Inspect) Jun 21, 2025 7:31pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 21, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added the Dashboard Involves changes to the Dashboard. label Jun 21, 2025
@jnsdls jnsdls marked this pull request as ready for review June 21, 2025 18:44
@jnsdls jnsdls requested review from a team as code owners June 21, 2025 18:44
Copy link
Member Author

jnsdls commented Jun 21, 2025


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • merge-queue - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@codecov
Copy link

codecov bot commented Jun 21, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 52.06%. Comparing base (0ce5f79) to head (4e8918d).

Additional details and impacted files
@@                 Coverage Diff                 @@
##           graphite-base/7406    #7406   +/-   ##
===================================================
  Coverage               52.06%   52.06%           
===================================================
  Files                     945      945           
  Lines                   63565    63565           
  Branches                 4208     4208           
===================================================
  Hits                    33098    33098           
  Misses                  30361    30361           
  Partials                  106      106           
Flag Coverage Δ
packages 52.06% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@jnsdls jnsdls force-pushed the Move_Sentry_config_to_instrumentation-client.ts branch from d3b03a2 to 0ce5f79 Compare June 21, 2025 18:47
@jnsdls jnsdls force-pushed the _Dashboard_Replace_Sentry_Replay_with_PostHog_integration branch from 2bd27b7 to 4e8918d Compare June 21, 2025 18:47
@vercel vercel bot temporarily deployed to Preview – nebula June 21, 2025 18:47 Inactive
@vercel vercel bot temporarily deployed to Preview – wallet-ui June 21, 2025 18:47 Inactive
@vercel vercel bot temporarily deployed to Preview – thirdweb_playground June 21, 2025 18:47 Inactive
@vercel vercel bot temporarily deployed to Preview – docs-v2 June 21, 2025 18:47 Inactive
@github-actions
Copy link
Contributor

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 62.56 KB (0%) 1.3 s (0%) 592 ms (+56.93% 🔺) 1.9 s
thirdweb (cjs) 350.74 KB (0%) 7.1 s (0%) 2.8 s (+2.7% 🔺) 9.8 s
thirdweb (minimal + tree-shaking) 5.72 KB (0%) 115 ms (0%) 86 ms (+345.02% 🔺) 201 ms
thirdweb/chains (tree-shaking) 530 B (0%) 11 ms (0%) 52 ms (+634.92% 🔺) 62 ms
thirdweb/react (minimal + tree-shaking) 19.61 KB (0%) 393 ms (0%) 93 ms (+71.78% 🔺) 485 ms

@jnsdls jnsdls changed the base branch from Move_Sentry_config_to_instrumentation-client.ts to graphite-base/7406 June 21, 2025 18:56
@graphite-app
Copy link
Contributor

graphite-app bot commented Jun 21, 2025

Merge activity

### TL;DR

Replaced Sentry Replay integration with PostHog Sentry integration in the dashboard app.

### What changed?

- Removed the Sentry Replay integration that was blocking media and masking text
- Added PostHog Sentry integration with organization set to "thirdweb-dev" and projectId set to 6690186
- Updated the comment to indicate the integration of Sentry with PostHog

### How to test?

1. Verify that Sentry events are properly forwarded to PostHog
2. Check that the PostHog dashboard shows Sentry events from the thirdweb-dev organization
3. Confirm that error tracking continues to work as expected

### Why make this change?

This change integrates Sentry with PostHog to consolidate analytics and error tracking data in one platform. This will provide better correlation between user behavior and errors, improving our ability to diagnose issues and understand their impact.

<!-- start pr-codex -->

---

## PR-Codex overview
This PR focuses on integrating Sentry with PostHog in the `instrumentation-client.ts` file, replacing the previous Sentry Session Replay configuration.

### Detailed summary
- Removed the previous Sentry replay integration configuration.
- Added `posthog.sentryIntegration` with specified `organization` and `projectId`.

> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`

<!-- end pr-codex -->
@graphite-app graphite-app bot force-pushed the _Dashboard_Replace_Sentry_Replay_with_PostHog_integration branch from 4e8918d to c09123d Compare June 21, 2025 19:23
@vercel vercel bot temporarily deployed to Preview – docs-v2 June 21, 2025 19:23 Inactive
@vercel vercel bot temporarily deployed to Preview – wallet-ui June 21, 2025 19:23 Inactive
@vercel vercel bot temporarily deployed to Preview – nebula June 21, 2025 19:23 Inactive
@vercel vercel bot temporarily deployed to Preview – thirdweb_playground June 21, 2025 19:23 Inactive
@graphite-app graphite-app bot changed the base branch from graphite-base/7406 to Move_Sentry_config_to_instrumentation-client.ts June 21, 2025 19:23
Base automatically changed from Move_Sentry_config_to_instrumentation-client.ts to main June 21, 2025 19:31
@jnsdls jnsdls merged commit 5bc50eb into main Jun 21, 2025
11 checks passed
@jnsdls jnsdls deleted the _Dashboard_Replace_Sentry_Replay_with_PostHog_integration branch June 21, 2025 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Dashboard Involves changes to the Dashboard.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants