-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
Labels
Comments
Hey @nhorton ! Thanks for the idea. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: