Sentry: Stride (HipChat replacement) intergration

Created on 26 Feb 2018  ·  9Comments  ·  Source: getsentry/sentry

We were forcibly upgraded from HipChat to Stride over the weekend and this has unfortunately broken all our integrations, the most important of which is Sentry.

Please can a native Stride integration be developed ASAP?

This might be of help https://developer.atlassian.com/cloud/stride/learning/hipchat-to-stride/

Thank you

Most helpful comment

I look forward to native integration. In the meantime I feel this helps:

  • Create an incoming webhook with Unified Webhooks Stride app

  • Configure that webhook on Sentry > Project > Settings > Alerts > Slack > Webhook URL

All 9 comments

Just so everyone who might be watching is aware, we're going to look into Stride, but to be perfectly honest its (right now) at the bottom of some of our other concerns. We're intending to launch many overhauled integrations on top of our new platform in the next few months, but Jira, GitHub, and Slack (to name a few) are the priorities right now. Hopefully with the new scaffolding the time needed to build (and maintain) these will be drastically reduced, as historically it's been quite complex for things like HipChat.

Any update on Stride?

Our company migrated from Slack to Stride, but the lack of integration with Sentry is really annoying. It would be nice if there was some update on this, even if it was a minimal integration.

Everyone needs to realize that Sentry has a lot of important things to build, and integrations with every new product aren’t high on that list. We’re in the middle of overhauling the rest of the ecosystem and will be evaluating Stride when that is done. Bumping a GitHub thread isn’t going to make that happen any faster.

Thanks @dcramer we understand that, the only thing is that Stride is not really just a part of "every new product". Everyone using HipChat is being migrated from HipChat to Stride against their will by Atlassian. This means that it's not just some new product that may or may not become popular, but will gradually become approximately as popular as HipChat is (but probably more as frankly it's better)... and your current HipChat integration will become defunct.

I totally get that we don't get to dictate the roadmap for Stride and that the work your doing overhauling the ecosystem makes sense to come first, but I'd hope that once that framework is in place you give this some level of priority as at the moment you're making all your happily HipChat-integrated customers unhappy (although we get that it's more Atlassian's fault than Stride's).

I hope that the above makes sense and that Sentry realise that Stride is not just some random new team chat product, but what all HipChat users will be using soon. And 👎 to Atlassian for not making it backwards compatible with HipChat notifications, yet still forcing us to migrate - that was really irritating.

@violuke yeah we realize that its not really a choice for some people, and it is something we want to solve soon. It's just lower on our list of priorities purely on the customer demand side. I'm hoping we'll be able to resolve it in 60-90 days, but thats assuming timelines work out on other projects which often slip in engineering 🤦‍♂️

+1 - we are in the same boat. We are being force-migrated from Hipchat and we will lose notifications for sentry. is there a way we can wire up using something else ?

I look forward to native integration. In the meantime I feel this helps:

  • Create an incoming webhook with Unified Webhooks Stride app

  • Configure that webhook on Sentry > Project > Settings > Alerts > Slack > Webhook URL

Was this page helpful?
0 / 5 - 0 ratings