getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
39.1k stars 4.2k forks source link

Make msteams integration available to on premise installations #70458

Closed mw-cyrano closed 6 months ago

mw-cyrano commented 1 year ago

Problem Statement

We followed these instructions to install the msteams integration for a Sentry on premise installation: https://develop.sentry.dev/integrations/msteams/

However, the integration can't be installed, as it seems to be only available to sentry cloud.

When activating the plugin on the side of Microsoft Teams, during the setup process, we're redirected to sentry.io. It lacks the possibility to change the URL to a on prem server.

It is possible to connect a sentry on premise installation to MSteams?

Solution Brainstorm

No response

Product Area

Settings - Integrations

getsantry[bot] commented 1 year ago

Assigning to @getsentry/support for routing ⏲️

hubertdeng123 commented 1 year ago

What version are you using? this seems to be a similar issue here so I'm wondering if this is still an issue in a newer version of self-hosted. https://github.com/getsentry/sentry/issues/20834

getsantry[bot] commented 6 months ago

Assigning to @getsentry/support for routing ⏲️

mw-cyrano commented 1 year ago

The other issue is mainly about the setup of a custom app and a custom bot in teams and how to connect it to your sentry installation. That works, it's a bit bumpy, but we made it work.

However, it would be much easier, if the public sentry app in the Microsoft Store would be extended in a way it also supports custom installations. So far you can either use the public app with sentry.io or set up your own app and use it with your on premise installation. It would be much neater, if you could just select the domain during the setup of the public app and direct it to your on premise installation. That's what this feature request is about.

If that was possible, on premise installation could be connected in minutes instead of hours with the custom app solution.

azaslavsky commented 1 year ago

Just so that it's easier for us to debug: what version are you on?

mw-cyrano commented 1 year ago

The version reported is:

image

azaslavsky commented 1 year ago

When you open your self-hosted instance to the root path, there should be a version number in the grey bar at the bottom right corner (not in the purple sidebar, but just inside of it). What is that number?

mw-cyrano commented 1 year ago

The sentry version is 23.10.0 dev 086000e7.

However, the public sentry connection bot in the Microsoft Store does not at all give you the chance to connect it to on premise sentry installations, as it always redirects to sentry.io. So to my understanding, it doesn't support on prem, because how would I connect it to one?

azaslavsky commented 1 year ago

Can you link to the Microsoft store page for the Sentry bot (the one you took a picture of)? I'm trying to figure out if this is an internal or external project.

mw-cyrano commented 1 year ago

It's this one: https://admin.teams.microsoft.com/policies/manage-apps/5adee720-30de-4006-a342-d454317db1d4

(I think you might have to be logged in to MS Teams to access this link.)

hubertdeng123 commented 1 year ago

I'm going to backlog this item, since it's not something that we can prioritize right now. Thanks for filing this with us though.

sbussweiler commented 6 months ago

Are there any estimates when this feature will be implemented? The integration of an on-premise Sentry solution is a common use case. It would be great if the public Sentry app supported this.

getsantry[bot] commented 6 months ago

Routing to @getsentry/product-owners-settings-integrations for triage ⏲️

scefali commented 6 months ago

@mw-cyrano

However, it would be much easier, if the public sentry app in the Microsoft Store would be extended in a way it also supports custom installations.

That is not how any of our other apps work like GitHub, Jira, Slack, etc that use redirects. In every case, you have to set up your own app in that service to use it in Self-hosted. As you have pointed out, it's because of the redirect. My understanding is that it would take a change on Microsoft's end to make this work so even if we wanted to do this, we probably couldn't. This is why running self-hosted is hard and why Sentry has a SaaS offering so you can pay us to have it the easy way.