Reporting to Sentry to proof that it's working, like on start up?

Question

We are using Sentry for finding some errors.

How do you proof, that a reporting is working?
I had a Spring-Boot project, which was not sending any error to Sentry, so it looks like it was working without an error, but I saw in Kibana, that there have been errors.
So, my configuration was wrong. After fixing the setup, it's now sending the errors to Sentry too.

Is there any way to proof that the sending to Sentry is working?
Something like on startup of my Spring-Boot application sending a first string?

I found 2 possible solutions which both sucks, so that's why I ask for a more professional way:

1. I can make just on application start up a log.error("sentry is working")
2. I can set the log-level from warning / error to info just to see that it's working and if see it in Sentry, you change it back?

But as i mentioned, both methods are not good, so let me know how you are resolving problems like this are unprofessional to me, so let me know

Answer 1

There isn't a real "answer" here currently, as part of Sentry's simplicity is it doesn't do anything until an error happens. One potential solution is to introduce a path like example.com/500 that deliberately errors.