How to Get Alerted on Slack When Your Site Goes Down

Email alerts are fine. But when your site goes down at 9am on a Tuesday, you want to know in the same place your team is already talking — Slack. A message in your #incidents channel is impossible to miss. An email to a shared inbox is very easy to miss.

This guide walks you through connecting Acumen Logs to Slack so your entire team gets notified the moment something goes wrong, with enough context to start investigating immediately.

What You'll Set Up

• A Slack alert channel connected to Acumen Logs
• Uptime, API, and heartbeat monitors sending to Slack
• Custom alert rules so you control the noise level

Step 1: Create a Slack Incoming Webhook

1. Go to api.slack.com/apps and click Create New App
2. Choose From scratch, name it something like “Acumen Logs Alerts”, and select your workspace
3. In the left sidebar, click Incoming Webhooks and toggle it On
4. Click Add New Webhook to Workspace
5. Choose the channel you want alerts to post to (e.g. #incidents, #monitoring, or #engineering)
6. Copy the webhook URL — it'll look like https://hooks.slack.com/services/T.../B.../...

Step 2: Add the Webhook to Acumen Logs

1. Log in to your Acumen Logs dashboard
2. Go to Settings > Alert Channels
3. Click Add Channel and select Slack
4. Paste your webhook URL
5. Give the channel a name (e.g. “Engineering Slack”) so you can identify it when assigning to monitors
6. Click Test — you should see a test message appear in your Slack channel within a few seconds
7. Save

Step 3: Assign the Alert Channel to Your Monitors

Connecting Slack doesn't automatically send alerts from all monitors — you assign channels per monitor, which gives you fine-grained control.

For each monitor you want alerting to Slack:

1. Open the monitor settings
2. Find the Alert Channels section
3. Select your Slack channel from the dropdown
4. Save

You can also set different channels for different monitors. For example, your checkout monitor might alert #incidents, while a low-priority marketing page monitor might only alert #monitoring-low-priority.

Step 4: Configure Alert Sensitivity

By default, Acumen Logs alerts you on the first failure. For some monitors, especially ones checking endpoints that occasionally flicker, you might want to require 2 or 3 consecutive failures before alerting. This reduces false alarms.

In your monitor settings, find Alert after N consecutive failures and adjust accordingly:

• Critical infrastructure (auth, payments): alert after 1 failure
• Non-critical pages: alert after 2–3 failures

What the Slack Alert Looks Like

When a monitor fails, your Slack channel will receive a message containing:

• The monitor name and URL
• The type of failure (timeout, wrong status code, content mismatch)
• The timestamp
• A direct link to the monitor in your Acumen Logs dashboard

When the monitor recovers, you'll get a follow-up message confirming the issue is resolved — so your team knows they can stand down.

Pro Tip: Use Separate Channels by Severity

As your monitoring setup grows, consider organising alerts by severity:

• #incidents-critical — payment flows, auth, core API
• #incidents-warning — secondary pages, non-critical APIs
• #monitoring-heartbeats — background job health

This way, your on-call engineer knows that a message in #incidents-critical needs immediate attention, while #incidents-warning can wait until morning.

Final Thoughts

Slack alerts turn monitoring from a passive dashboard into an active team workflow. When your whole team can see the moment something goes wrong — and the moment it recovers — incidents get resolved faster and nothing slips through the cracks.

Five minutes of setup. Worth it every time.

Key Takeaways

• Directing alerts to dedicated Slack channels ensures the entire engineering team has immediate visibility into outages.
• Rich incident notifications with error payloads and response timestamps speed up initial triage and root cause analysis.
• Configuring multi-location confirmation before triggering alerts eliminates false positives caused by local network blips.