[SOLVED] Enabling Sentry on self-hosted instance

Hi guys - I'm trying to enable Sentry on my self-hosted instance but I'm having issues getting the values I need to set.

On the documentation it looks like I can just modify the .env file and supply the following:

From the environment variables documentation - the _APP_LOGGING_CONFIG should be set to SENTRY_API_KEY;SENTRY_APP_ID. I can't find these two at all. There was something about the SENTRY_API_KEY being no longer available for new accounts as it is already deprecated. Can anyone tell me which page to go to so I can grab these values? I really want to use Sentry on my instance.

Check this
https://discord.com/channels/564160730845151244/1127577801009152092/1127577801009152092

Thank you, it works for me now! It looks like on the DSN you can get those values:

Considering people do ask about it, maybe the documentation needs to improve a bit.

cc @VincentGe

🤣 what if I told you I didn't even know we had sentry support

Marking for docs and for a twitter thread 🤣 If I didn't know, must be many others

And its sooo useful...

🤣🤣 I'm literally trying to track down where the heck all the 500s are coming from

As we speak

It's a mini-mistery cause internal server error is not an acceptable error message

anywhere

Also just more clnt side/real time verification

I shouldn't need to make a request before being yelled at that my phone number is formatted wrong

Yes, usually, most times I'm like, well, yes, I know it's a server error, but what I'm doing wrong? So that's why I started using sentry, and sincerely, one of the best features I have discovered

Hahah
Yes, like in many cases it does so much verifications and at the end its like "Oh, wait a second this is just 7 digits number wts?"

🤣 we share your pain. The solution is just not trivial 🙃

[SOLVED] Enabling Sentry on self-hosted instance