Skip to content
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

Configure Sentry releases #3116

Open
sarayourfriend opened this issue Oct 2, 2023 · 0 comments
Open

Configure Sentry releases #3116

sarayourfriend opened this issue Oct 2, 2023 · 0 comments
Labels
🤖 aspect: dx Concerns developers' experience with the codebase 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: frontend Related to the Nuxt frontend 🔒 staff only Restricted to staff members

Comments

@sarayourfriend
Copy link
Collaborator

Problem

We do not upload frontend source maps or releases to Sentry. This prevents the Sentry UI from being able to identify where in the code an exception actually happened or tell us when an issue is related to a new release/if a new release is unhealthy.

Description

We should try to use the Nuxt plugin's publishRelease settings to enable this: https://sentry.nuxtjs.org/configuration/options/#publishrelease

Note that git-related settings will not work because we build the application inside a docker container without the git repository available.

We could change that by building the application on the CI box instead of inside a container and then copying the release in (this might actually simplify things for us, with the frontend, considering the complexities we have with build contexts for it) but that's work for a separate issue, if we do it at all (it has its own trade-offs).

Finally, it isn't clear to me whether doing this will automatically make source map uploads work. The Nuxt plugin's documentation is not clear on this. We can try to get the releases working first and then check to see if the source maps are available. If they are, great! If not, then we need to figure out why. They're available on the actual website, publicly, but Sentry recommends uploading and associating them with a specific release because it can them more reliably associate the line of code for a release for a given event.

@sarayourfriend sarayourfriend added 🟨 priority: medium Not blocking but should be addressed soon 🤖 aspect: dx Concerns developers' experience with the codebase 🔒 staff only Restricted to staff members 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🧱 stack: frontend Related to the Nuxt frontend labels Oct 2, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Openverse Backlog Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🤖 aspect: dx Concerns developers' experience with the codebase 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: frontend Related to the Nuxt frontend 🔒 staff only Restricted to staff members
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant