Add Sentry error reporting to install.sh #740
Comments
|
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
|
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
|
@armenzg has a blog post coming out about how the Developer Productivity team did something very similar with our environment bootstrapping script. Inspo! |
This is the MVP of error monitoring of the self-hosted installer. We have: - Added a prompt for users to opt into error reporting - Rewritten the traceback code to give a full stack trace - Hooked up sending errors to our self-hosted instance Fixes #740 Co-authored-by: Chad Whitacre <[email protected]> Co-authored-by: hubertdeng123 <[email protected]>
|
I'm going to reopen this because there are many more details we need to pay attention to in order to not piss off users with this change. |
|
Sorry ... we've got getsentry/team-ospo#36 as our meta ticket. |
Summary
sentry-clihas a Docker image and Bash signal trap support: https://docs.sentry.io/product/cli/send-event/#bash-hookThe two didn't play well together but now this can be overcome: getsentry/sentry-cli#852
Hence, we should try this out and see if it is useful to catch unknown issues in the wild.
Motivation
We rely on people to report issues with the install script and provide relevant logs along with that. This has worked okay so far but the process is very manual, cumbersome, and relies on the users reporting issues. Sentry was created to solve these issues to why not dog food?
The text was updated successfully, but these errors were encountered: