-
Notifications
You must be signed in to change notification settings - Fork 2k
Add sentry logging to multi-site dashboard #106852
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
p-jackson
wants to merge
1
commit into
trunk
Choose a base branch
from
add/sentry-logging-msd
base: trunk
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| import { initSentry } from '@automattic/calypso-sentry'; | ||
| import type { User } from '@automattic/api-core'; | ||
| import type { AnyRouter } from '@tanstack/react-router'; | ||
|
|
||
| export function setupErrorLogging( user: User, router: AnyRouter ) { | ||
| initSentry( { | ||
| userId: user.ID, | ||
| beforeSend: ( event ) => { | ||
| const lastMatch = router.state.matches.at( -1 ); | ||
| const site_slug = lastMatch?.params?.siteSlug; | ||
| const full_path = lastMatch?.fullPath; | ||
|
|
||
| event.tags = { | ||
| site_slug, | ||
| full_path, | ||
| ...event.tags, | ||
| }; | ||
|
|
||
| return event; | ||
| }, | ||
| } ); | ||
| } | ||
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 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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In v1, we're logging the
blog_idas well. I don't know but should we somehow support it in v2 as well 🤔There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could do a similar trick to what we do in the tracks code, which is to search through the query cache to see if we happen to know what the blog id is. But there I was worried about keeping compatibility with old tracks.
Here, I figured a new error log was something a dev would debug without any reference to what an equivalent error looked like in v1. So there's no need to have backwards compatibility. Grabbing the
siteSlugis more robust and gives the dev doing the debugging basically the same information.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm still looking into Sentry though. I'm wondering whether we've actually deactivated our Sentry account for Calypso 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Sentry account is still active, with an active subscription.