New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
statuspage.io integration? #5868
Comments
Can you explain more what you have in mind for how to integrate Zulip with it? Should be doable with our incoming and outgoing webhooks, how much work it is depends mostly on their API. |
Hello @zulip/server-bots, @zulip/server-integrations members, this issue was labeled with the area: bots, area: integrations labels, so you may want to check it out! |
@timabbott Sure! I guess it would be pretty similar to PagerDuty, where you would receive a Zulip message when an incident is created. And you could use a Zulip command to trigger an incident to get created yourself. Except whereas Pagerduty is only an internal tool, statuspage.io is intended to be subscribed to by your customers. So you could subscribe to get updates from someone's status page, like you could subscribe to get zulip updates from a twitter feed. Hope that makes sense! |
Cool. @geekdave is this something you're interested in working on? zulip.readthedocs.io/en/latest/integration-guide.html covers in the incoming-to-Zulip webhook side, which should be quite easy with their API. The second half should use our brand new outgoing webhooks; I'd recommend doing that after the incoming part is all done though :) |
@zulipbot claim |
@geekdave @timabbott As for implementing 1st part, i guess the fixtures we need for incoming webhook should be extracted from this page : https://doers.statuspage.io/ as they have api endpoints for incidents, subscribers, metrics, users etc.. am i thinking it right..??? |
Okay as i took a deep look inside statuspage i came to know that statuspage sends notifications to its subscribers via webhook only in two scenarios :
|
@timabbott @geekdave here is the test output Uppermost output is when an incident is created, middle one when that incident is updated and bottom most output when a component's state gets changed... Is it okay ...am i missing something. |
I'm no longer actively using Zulip, so I won't be in a position to test this feature. But the above output looks like exactly what I had in mind earlier this year! Thanks! |
Hello @Rishabh570, you claimed this issue to work on it, but this issue and any referenced pull requests haven't been updated for 10 days. Are you still working on this issue? If so, please update this issue by leaving a comment on this issue to let me know that you're still working on it. Otherwise, I'll automatically remove you from this issue in 4 days. If you've decided to work on something else, simply comment Thank you for your valuable contributions to Zulip! |
I already opened up a PR. |
Hello @Rishabh570, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 14 days. You can reclaim this issue or claim any other issue by commenting Thanks for your contributions, and hope to see you again soon! |
Incoming webhook part of statuspage.io is done... |
Yeah, I'm going to close this as complete; the incoming webhook is much of the value here. |
Is it possible to integrate zulip with statuspage.io, both for
The text was updated successfully, but these errors were encountered: