Statuspage updates posting to a Slack thread
Asked by Derek George:

With the Statuspage / Slack Integration, I'm wondering if it's possible to configure the Slack posts in the following manner:

1. When a new incident is created in Statuspage a new post is then created in the desired Slack channel
2. Any status updates added to the incident are then threaded off of the above Slack post

Is this possible? Currently all status updates are added as new posts in the Slack channel and this is less desirable in my situation because it creates too much noise.

Thank you


Answers:
author: Jesse Klein
body: Hi Derek,

This is Jesse from the Statuspage support team. Welcome to the community! While we currently don't have a way to thread the incidents in Slack, if you are using the [Slack integration](https://support.atlassian.com/statuspage/docs/set-up-a-slack-integration/) that is meant for team members, you can limit what is being shown on those posts to a particular channel.

If you are using [Slack subscriptions](https://support.atlassian.com/statuspage/docs/enable-slack-subscriptions/), though, the posts are treated like other subscriptions and would be less configurable compared to integration.

I'm curious about what posts are being added to your Slack channel and which parts are considered noisy to you. It could be worth writing a feature request to help reduce the noise. I'd love to hear your thoughts and use case!

Regards,  
Jesse

comments: author: Derek George
body: Appreciate the response, Jesse

For my use case, I have one Slack channel where all incidents will post to for visibility to stakeholders. I have additional external vendors that already post in the incident channel and they are set up to post once for the creation of the incident and then all status updates are threaded off of that post. I am hesitant to set up our Statuspage Slack integration into that incident channel because status updates will get posted as new posts each time in that channel rather than threaded, so that's my concern of being too noisy in relation to our other integrations already working.

Happy to chat more here if there's a potential solution. Otherwise, please let me know if I should write a feature request. Thanks!


author: Jesse Klein
body: Hi Derek,

Thanks for providing that use case. I created a feature request with our development team under STATUS-630. Statuspage doesn't currently have a public suggestion board but if you have a question, you can reference this ticket. I tried to see if there were any workarounds that would work and the only thing would be to mute posts from Statsupage but then that would defeat the purpose of getting the original incident.

I think the feature request is the way to go on this one. Please let me know if you have any other questions about this.

Regards,  
Jesse


author: Derek George
body: Ok. Thanks for writing up the feature request. Appreciate the help!


author: danish_din
body: Hey,

Would love this feature

Any progress with this?


author: siva
body: Any update on this feature please ?

Especially github status messages are very noisy.


author: Matthew Hennesy
body: Hello Siva,

I'd be happy to provide an update!

STATUS-630 is still under consideration for the future roadmap.

Thanks,  
Matthew


author: Kinnaird McQuade
body: Hi [@Matthew Hennesy](/t5/user/viewprofilepage/user-id/5069494) - we are also very interested in this feature. It would help users avoid alert fatigue. For us, we have a dedicated Slack channel for vendor downtime. In this example, there are 20-30 messages per day from various 3rd party vendors reporting incidents. This floods the slack channel. Preferably, as a user I should only be notified if (1) there is a new incident, or (2) I see an incident that I wanted to follow and I followed it.

I recorded a Loom video of scrolling through our slack channel that subscribes to several 3rd party vendors who use Statuspage. It's gotten very unruly very quickly. I think Atlassian could fix this easily by supporting threads. I hope this helps!

<https://www.loom.com/share/56fed7ce38584217a561b6c683764a14>


author: Jesse Klein
body: Hello Kinnaird,

Thanks for providing the Loom video. I have attached this to the feature request to share with engineering. I can totally understand where the alert fatigue can come from. Thanks again for this.

Regards,  
Jesse


Tags: slack