Skip to content
Xplorr Docs

Channel Routing: Which Slack Channels Receive What

Channel Routing

Section titled “Channel Routing”

Channel routing decides which Slack channels receive Xplorr’s scheduled messages. Today it sends the daily digest and weekly summary to a list of channels. Scoping each channel to its own accounts, tags or services is being built.

What works today

Section titled “What works today”

An organization can have several channel routes. Each route names a Slack channel and has a digest switch.

  • The daily cost digest and the weekly executive summary are posted to every route whose digest switch is on.
  • When no routes exist, they go to the Slack workspace’s default channel.
  • Every routed channel receives the same organization wide digest.

Routes are not yet editable in the console. There is no public Xplorr API, so to set up routes, contact the Xplorr team with the channels you want.

Where other notifications go

Section titled “Where other notifications go”

Anomaly alerts, budget alerts, alert rule triggers and credit alerts do not use routes. They are posted to the Slack workspace’s default channel through the Xplorr Slack app, or to the organization’s Slack webhook (or a rule’s own webhook) when the app is not available.

Being built

Section titled “Being built”
  • Per channel scope: limiting a channel to specific cloud accounts, services or tags, so #platform-team sees only the production AWS account. Routes already store a scope, but the digest does not apply it yet.
  • Per channel notification types: routing anomalies and alert rule triggers to specific channels. Routes store these switches, but nothing reads them yet.
  • Console settings for creating and testing routes.
  • Microsoft Teams channels, with the Teams bot.
Section titled “Related guides”