Slack
Send analysis results to a Slack channel using an incoming webhook
Connect a Slack channel using an incoming webhook URL. Each Slack channel you want to deliver to gets its own webhook, and each webhook becomes a separate SigSentry notification channel.
This page covers outbound notifications — delivering analysis
results to Slack. For inbound commands (running analyses from
Slack with /sigsentry analyze), see
Slack chat triggers.
Prerequisites
| Need | Notes |
|---|---|
| Slack workspace | You need permission to install apps |
| A target channel | The channel SigSentry will post to |
Setup walkthrough
Create a Slack app (or use an existing one)
Go to api.slack.com/apps and click Create New App → From scratch.
| Field | Value |
|---|---|
| App name | SigSentry |
| Workspace | Pick yours |
Click Create.
Enable Incoming Webhooks
In the app's left sidebar, click Incoming Webhooks and toggle Activate Incoming Webhooks to on.
Add a webhook for a specific channel
Scroll to the bottom and click Add New Webhook to Workspace. Pick
the channel you want SigSentry to post to (e.g. #engineering-alerts)
and click Allow.
A new webhook URL appears in the table — copy it. It looks like:
https://hooks.slack.com/services/T01.../B02.../xxxxxxxxxxxxxxxxxxxxAdd the channel in SigSentry
In the dashboard, Project → Channels → Add Channel.
| Field | Value |
|---|---|
| Type | Slack |
| Name | Descriptive label, e.g. #engineering-alerts |
| Webhook URL | The Slack webhook URL you just copied |
| Severity threshold | Lowest severity that should trigger this channel |
Save and test
Click Save. To verify, run a test analysis on the project — you should see a Slack message land in the channel with the diagnosis summary.
What gets posted
Each Slack message includes:
- A severity badge color-coded by level (red / orange / amber / blue / grey from critical to info)
- The analysis summary
- The root cause and affected services
- A "View full analysis" button linking back to the dashboard
Multiple channels per project
You can connect multiple Slack channels to the same project — for
example a low-noise #oncall-critical (threshold: critical) and a
busier #engineering-alerts (threshold: high). Each is a separate
SigSentry notification channel with its own webhook URL.
Webhook security
Slack incoming webhooks are unauthenticated public URLs — anyone with the URL can post to your channel. Treat them like secrets:
- Don't paste them into public repos or shared docs
- If a URL leaks, revoke it in Slack (under the app's Incoming Webhooks page) and update the SigSentry channel with a new one
Troubleshooting
| Error | Fix |
|---|---|
400 invalid_payload | Slack rejected the message format; usually transient — retry. If persistent, regenerate the webhook |
404 channel_not_found | The Slack channel was deleted; recreate the webhook in a different channel |
429 rate_limited | Slack throttling; SigSentry retries with backoff automatically |
| Messages not arriving | Check the webhook URL hasn't been revoked in Slack |