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

Validate connection API #2066

Open
nhorton opened this issue Jul 11, 2023 · 1 comment
Open

Validate connection API #2066

nhorton opened this issue Jul 11, 2023 · 1 comment

Comments

@nhorton
Copy link

nhorton commented Jul 11, 2023

Describe the idea
Right now, the only way to validate that things are well-configured is to do a capture_message call (per your docs) and then go look at the Sentry UI.

It would be very helpful to have an api like Sentry.validate_configuration that checked the settings locally and then actually phoned-home as well to make sure that the DSN and such were good.

Why do you think it's beneficial to most of the users
This would let one programatically confirm all was well. It would be very helpful in a diagnostics page in the app (important thing we have and care about) but also things like Helm chart tests.

Possible implementation
You could just do a capture_message internally but just wrap it in something blocking that confirms the transmission actually happened successfully. That would almost be ideal as it is the "real" codepath. Then on the back-end, you could filter those messages out, or even just default them to Ignored.

@antonpirker
Copy link
Member

Hey @nhorton !

Thanks for the idea.
Something like this has been coming up in the past but the details have never been fleshed out. So I will bring this up again in our internal meetings. @sl0thentr0py is on a conference right now it it can take a week or so until I can discuss this with him and the others.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Waiting for: Product Owner
Development

No branches or pull requests

3 participants