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 support for Issues and Performance #2152

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dwd
Copy link
Member

@dwd dwd commented Nov 27, 2022

I've been working on this for a few weeks, and it'll take a lot more work, but I thought it was worth opening a Draft PR for visibility.

Note that this is utterly useless with Sentry-SaaS unless you have deep pockets - I'm running it for my server against a self-hosted Sentry - but I'm generating a transaction per stanza, currently, as well as for S2S connections and more.

@guusdk
Copy link
Member

guusdk commented Nov 28, 2022

My immediate concern is that we're adding an awful lot of very specific code right into pretty core code, to facilitate a very specific, proprietary API. Is there any way to make this a lot less invasive, from a code perspective? Move things to a plugin, or at least a set of dedicated classes, for example by introducing generic interfaces, that then can be used by more specific code)?

It's nice to see something like this materialize though. Back in the day, we created a much less versatile solution that shot things straight into JIRA. That was surprisingly crude but effective.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants