zlacker

[parent] [thread] 3 comments
1. Macuyi+(OP)[view] [source] 2023-06-29 18:09:22
Very good points. Meanwhile I have clients asking me why they can't have a status page to which I reply: you can, but ultimately to be completely fail proof it will be a human updating it slowly. To which they reply: but GitHub or X does it...

Very infuriating, that.

replies(1): >>AYBABT+J1
2. AYBABT+J1[view] [source] 2023-06-29 18:15:47
>>Macuyi+(OP)
There's some nice tooling these days for this. E.g. https://firehydrant.com/ and https://incident.io both make this a faster, more embedded process.
replies(2): >>sjwhit+r8 >>amanda+vK
◧◩
3. sjwhit+r8[view] [source] [discussion] 2023-06-29 18:46:32
>>AYBABT+J1
Hey, incident.io CEO here! Thanks for mentioning us.
◧◩
4. amanda+vK[view] [source] [discussion] 2023-06-29 21:54:08
>>AYBABT+J1
And Jeli.io for this! With the Statuspage integration, you can set the status, impact, write a message for customers, and select impacted components all without leaving Slack. Statuspage gets updated with a click of a button.
[go to top]