Limitations of self-hosted Sentry

[misleb]

I am planning on demoing Sentry to my company as a replacement for a more limited homegrown system. For security reasons we need to ensure that our data doesn’t leave our networks. I want to ensure that onpremise doesn’t phone home or otherwise send out data to third parties other than explicit integrations. When I set up onpremise for the first time, it did ask about reporting data anonymously. I selected anonymous, but I’d like to turn that off completely. Is that possible?

Also, what limitations are there to self-hosted product? Can I still do Github and JIRA integration?

[BYK]

Hi @misleb!

Great to hear you are demoing Sentry to your company!

@misleb

For security reasons we need to ensure that our data doesn’t leave our networks.

If it is okay to use a cloud network (if your network is there too), you may be interested in the single-tenant solution too, just saying. /cc @matt

@misleb

I want to ensure that onpremise doesn’t phone home or otherwise send out data to third parties other than explicit integrations. When I set up onpremise for the first time, it did ask about reporting data anonymously. I selected anonymous, but I’d like to turn that off completely. Is that possible?

Absolutely: https://docs.sentry.io/server/beacon/ (that said the data reported is just aggregate metrics and helps us improve Sentry on-premise)

@misleb

Also, what limitations are there to self-hosted product? Can I still do Github and JIRA integration?

No limitations at all as sentry.io itself runs the same code that you get for on-premise. Then only thing is, right now the current stable release is 9.1.2 which is a bit behind. For latest features, updates, and fixes you may wanna try starting off from feat(sentry10): Make on-premise work for Sentry 10 by BYK · Pull Request #220 · getsentry/self-hosted · GitHub which should be fairly stable.