On-Prem Sentry Integration with On-Prem Azure DevOps Server

[SteffeyDev]

Summary

I was very excited to see that sentry integrates so well with Azure DevOps, but was sad to find, after installing Sentry on-prem, that I cannot integrate with my on-prem Azure DevOps server. Looking at the vsts integration code, it looks like most of the code would be the same for integrating with Azure DevOps server, with only a few changes in the authentication method needed (switching from OAuth to a different method that is supported by Azure DevOps Server, such as personal access tokens or another method from https://docs.microsoft.com/en-us/rest/api/azure/devops/?view=azure-devops-rest-6.1#create-the-request). With that in place, it would follow that the rest of the features carry over using the same API calls to the local Azure DevOps instance.

Motivation

Our company runs our own data center and keeps all data in-house, which necessitates using both on-prem sentry and on-prem devops. Many of the features of Sentry are connected to release management (such as sourcemap parsing and commit linking), which our team would benefit from having available. In addition, having the issue syncing would allow us to prioritize and track bugs more easily.

Thanks for your awesome product and consideration or this new feature!

┆Issue is synchronized with this Jira Improvement by Unito

[scefali]

@SteffeyDev It's definitely possible to do this, but we don't have the docs for it (yet).

[SteffeyDev]

Ok, that's good to hear, could you point me to an example config of someone doing it so I could try and figure it out?

[mahrmediait]

Hello!

Need this too. Did anybody have an idea how to realise it?

[SDohle]

I'm interested, too. Same setup here, on premise Sentry should interact with on premise Azure DevOps Server.

[ceorourke]

We published docs here but I'm unsure if it'll work for Azure Dev Ops Server since it's a different product.

[SteffeyDev]

AFAIK Azure DevOps server does not support OAuth, so not sure if this works. When I tried the published docs last it did not work.

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Accepted, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[SDohle]

Any news on this topic?

[failoman23]

Does Sentry have On-Premise Azure DevOps Integration on a roadmap?

[BYK]

Pinging @getsentry/ecosystem for triage

[manuzope]

Hi there, Azure DevOps Server is not on the roadmap right now. To be able to integrate with it, you can create an internal integration that will allow you to create tickets from Sentry.

Will log this as a feature request. If you want an Azure Devops Server integration, please add a 👍 to the ticket.

[SteffeyDev]

It is probably worth pointing out that "Azure Server" is not an actual product AFAIK, and abbreviating "Azure DevOps Server" to just "Azure" is very confusing as Azure is a cloud service provider, which is an entirely separate product and composed of hundreds of services, including DevOps Services (but not DevOps Server). If you must abbreviate, I recommend just "DevOps Server" or "TFS Server", as it used to be called.

[Nonobis]

Hello, any hope to see this integration working with Azure DevOps Server one day ?

[shadowstejo]

Any news?
@scefali

greetings from germany

[hubertdeng123]

There hasn't been any movement on this recently

[getsantry]

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

[Dhrumil-Sentry]

We don't have any concrete plans for this yet. We will keep this issue updated if there are any changes

[robheffo79]

3 years and still nothing on this one. It seems you got enough interest to warrant actually adding this to your feature line-up.

We're looking at using Sentry now and we REQUIRE integration with our On-Prem DevOps server.

[robheffo79]

Still waiting.. Still nothing. C'mon guys!

[sentaur-athena]

This is not on the team's roadmap in near future due to priority and the fact that customers have relatively easily workaround using internal integrations.