Skip to main content

​
Overview

Every vendor you depend on publishes status updates, and almost none of them affect you, until one does. Pipe them into one channel and let Roomote read each incident against your actual code: which SDKs you call, which regions you run in, and which features you use. You stop triaging vendor noise by hand and only hear about the outages that matter. This is how we run it at Roo.
  • Trigger: Channel event
  • Setup time: About 20 minutes
  • Requires: Admin access, Slack or Discord
  • Serves: On-call, Support
  • Cooked By: Matt Rubens

​
Ingredients

  • A Slack or Discord channel such as #vendor-status receiving vendor status feeds. Most vendors offer Subscribe via Slack, RSS-to-channel, or email-to-channel.
  • Auto-respond channels
  • An environment covering the repositories that use these vendors
  • Roomote invited to the channel on Slack, or able to see it on Discord

​
Steps

  1. Create #vendor-status and subscribe it to every upstream status page you care about.
  2. Invite Roomote to the channel.
  3. Under Settings > Automations > Auto-respond to channels, add the channel.
  4. Paste the launch criteria and instructions below.
  5. Post a fake incident and confirm a task launches. Then post a scheduled-maintenance notice and confirm it does not.

​
Launch criteria

Paste this into the channel’s Launch criteria field:

​
Instructions

Paste this into the channel’s Instructions field. Roomote gives these instructions to every task launched from the channel.

​
Variations

  • Name the vendors explicitly in the criteria to ignore feeds subscribed to just in case.
  • Ask Roomote to describe how to verify recovery whenever the verdict is Affects us.
  • Use a multi-repository environment so the usage search covers every service.
Auto-respond channels support Slack and Discord today. On Teams or Telegram, forward status events to a supported channel or mention Roomote from a workflow. Pairs well with: CI failure auto-fix · support channel