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

Add sentry.io error tracking #393

Open
ImUrX opened this issue Dec 15, 2022 · 5 comments · May be fixed by #1153
Open

Add sentry.io error tracking #393

ImUrX opened this issue Dec 15, 2022 · 5 comments · May be fixed by #1153
Labels
Priority: Normal The default priority Type: Enhancement Adds or improves a feature

Comments

@ImUrX
Copy link
Member

ImUrX commented Dec 15, 2022

I need opinions on others if this is a good idea, this basically sends errors to a server where we can see errors happening to the code, it works really well (it includes build info, backtracing and a lot more we can add ourselves) and it can be self-hosted.
This would require a Privacy Policy, the idea would be to have it disabled by default and add an opt-in option in the GUI somewhere, this would link to the privacy policy so the user can read it.

This would help a lot for finding errors that aren't actually getting reported by users and have a better tracking on the precise errors.
I don't find any cons tbh because it's disabled by default and it will be pretty helpful if it's actually enabled.

@TheButlah
Copy link
Contributor

TheButlah commented Dec 15, 2022

  1. Does sentry.io have good java integration? What about rust and typescript? can we use this same service across all parts of the tech stack?
  2. How much does this cost to use this as a service?
  3. Where do we host the service?
  4. What are some alternatives that we could consider in this decision?
  5. Would this include just errors, or would it also include other metrics? For example, frequency of user reset, amount of divergance from calibration position at reset time, etc, like things that can improve our understanding of if there were other subtle bugs introduced?

@TheDevMinerTV
Copy link
Member

TheDevMinerTV commented Dec 15, 2022

  1. Compatibility shouldn't be an issue 😅 image
  2. Depending on the tier, starting at $89/mo
  3. Some cheaper VPS, probably
  4. Sounds like a smart idea

4 should be 5 but I can't get it to be 5, so deal with it

@ImUrX
Copy link
Member Author

ImUrX commented Dec 15, 2022

  1. It's open source
  2. You can pay sentry.io or self-host it, we can try it before actually paying for it :P
  3. Maybe New Relic? But like sentry.io is open-source
  4. It's not automatic, it wont log errors that are catched. We need to add everything ourselves. It has a lot of features like breadcumbs that would help us give custom information for context-sensitive errors also

@TheDevMinerTV
Copy link
Member

New Relic is hella expensive

@ButterscotchV ButterscotchV added the Priority: Normal The default priority label Dec 16, 2022
@TheButlah TheButlah added Type: Enhancement Adds or improves a feature and removed Type: Feature Request labels Feb 12, 2023
@cleafspear
Copy link

regarding as someone who is a active user with sentry:
sentry has multiple pay tiers. they limit the amount of ingested data normally based on the pay tier you use, but the self-hosted edition does not have any limits on it, and is not cost, at the limitation that you will have community support for issues.
in regards to what data it collects? its entirely based on your error handler. you can have it provide anything you want in the logs, tho by default, it normally contains the following:
os type; hardware stats (cpu,gpu,ram) log level :error,warning,ect.,machine ID (only to match with other errors from the same machine, and a user UUID (only useful to id machines logged into with the exact same user/domain joined machines)
it is very useful to id what is going on and can give a statistic on what is causing the errors.

@ImUrX ImUrX linked a pull request Sep 3, 2024 that will close this issue
@ImUrX ImUrX linked a pull request Sep 3, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Normal The default priority Type: Enhancement Adds or improves a feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants