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

sentry #4

Open
1 of 2 tasks
hcientist opened this issue Jun 5, 2024 · 4 comments
Open
1 of 2 tasks

sentry #4

hcientist opened this issue Jun 5, 2024 · 4 comments

Comments

@hcientist
Copy link
Member

right now:

  • we'd like to know about errors for individuals before teachers need to write email
  • playwright tells us about demo
  • sentry tells about anyone in prod
    • tells what browser, user, session info, etc.

Need to:

  • read docs
    • sentry nextjs
    • might just need react doc

See slack for auth

  • note from matt: you need the auth during cli setup

Status:

  • Sentry is logging errors thrown from local dev (bare-metal) successfully
  • from prod

ToDo's (?)

  • The sentry docs should have info on configuring our monitoring. @hcientist do you have preferences on this?
  • During setup there is an option for bypassing browser extensions (notably, ad blockers), as they can cause errors to be intercepted/missed. I did not select this option, do we think it could cause issues down the line?
    • I presume it would not really be our place to tell teachers/students to disable their adblocker?
  • CI/CD - will error monitoring work in prod w/out additional changes?
    • During config, I selected no to CI/CD usage.
  • maybe check that monitoring catches from the devcontainers too
  • ensure nothing unexpected broke with sentry install... playwright?

See:

@hcientist hcientist converted this from a draft issue Jun 5, 2024
@hcientist
Copy link
Member Author

hcientist commented Jun 5, 2024

What more can we tell sentry, and how would we do it?

  1. environment?
    2. ${process.env.NODE_ENV}-${process.env.CODESPACE_NAME}
  2. user: on login and logout do the corresponding things from https://docs.sentry.io/platforms/javascript/guides/nextjs/enriching-events/identify-user/
  3. would be nice to have a sentry error when the user gets the private score issue:
    5. to artificially force the issue, edit your database by deleting a character from the sharingKey of whatever from a parttransposition, e.g. http://localhost:8000/admin/musics/parttransposition/313/change/
  4. maybe we should have a pre-build.sh that we run before next build, i.e. sh pre-build.sh && next build in the https://github.com/Lab-Lab-Lab/CPR-Music-mfwolffe/blob/sentry-tests/package.json#L5C13-L5C27
    7. write the current version to .env.local (e.g. from some git tag or git branch or git log commit hash output?

@hcientist
Copy link
Member Author

@mfwolffe where did we leave off? Perhaps given your computer troubles you'll have a harder time remembering than I do? (In which case, no worries)

@mfwolffe
Copy link
Collaborator

@mfwolffe where did we leave off? Perhaps given your computer troubles you'll have a harder time remembering than I do? (In which case, no worries)

I believe we shifted gears soon after I got sentry logging errors thrown in my bare metal dev environment. I'm not sure if anything is required config-wise to extend to dev/prod.

We were going to go through these 4 tasks next I believe.

mfwolffe added a commit that referenced this issue Oct 15, 2024
@mfwolffe mfwolffe removed their assignment Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In review
Development

No branches or pull requests

2 participants