How to Filter Slack Alerts by Severity and Time

If you’re using Slack for incident alerts, you probably know how fast things can get noisy. Not every alert needs to wake the whole team—or even show up in the same channel.

In this post, we’ll show you how to set up a clean, focused alerting flow with All Quiet and Slack. You’ll see how to:

• Route different severities to different Slack channels
• Mute low-priority alerts outside working hours
• Share critical alerts across multiple teams

All with minimal setup and maximum clarity.

---

TL;DR

You can make Slack work for your team, not against it. With All Quiet, you get:

• ✅ Team-level or Org level Slack integrations
• ✅ Severity-based filtering right in the integration
• ✅ Time-based muting with Routing Rules
• ✅ A shared channel for critical alerts across the org

Set it up once. Get focused alerts forever.

---

Why Filtering Slack Alerts Matters

Alert fatigue is real. When every minor issue gets the same visibility as a major incident, teams start tuning out. That’s bad for response times—and morale.

By filtering alerts smartly, you can:

• Keep team-specific channels focused
• Avoid after-hours noise for non-critical issues
• Escalate critical incidents to the right people, fast

The result? A Slack that actually helps your incident response, instead of getting in the way.

The Setup: Two Teams, One Shared Critical Channel

Let's imagine an organization with two teams:

• Frontend Team
• Backend Team

Each team manages its own monitoring stack, with separate on-call rotations and alert channels. But there’s one shared rule:

Critical incidents should reach both teams—no matter where they start.

Here’s how we want it to work:

Also:

• Minor alerts should be muted after hours and on weekends
• No cross-talk between teams for non-critical stuff

Now let’s see how to implement that in All Quiet.

Step-by-Step: Setting It Up in All Quiet

All Quiet gives you team-level separation, granular routing, and flexible Slack integrations. Here’s how to wire everything up:

1. Organize Teams Separately

In your Organization, create two teams:

• Frontend
• Backend

Each team has its own:

• Monitoring integrations (e.g. Datadog, Sentry, CloudWatch)
• On-call schedules
• Routing rules

This keeps alerts targeted and ownership clear.

2. Add Two Slack Integrations

Head to Outbound Integrations and create one slack integration per team. You’ll connect different channels based on what each team needs.

Frontend Slack Integration

• #frontend-alerts → receives warning and minor
• #incidents-critical → receives only critical

Backend Slack Integration:

• #backend-alerts → receives warning and minor
• #incidents-critical → receives only critical

🛠️ Important:

You control this right inside the integration settings. When adding a Slack channel, you choose which severity levels it should receive.

So:

• No routing rule needed to filter by severity
• Everything critical goes to #incidents-critical
• Non-critical stuff stays in team-specific channels

Easy.

3. Mute Low-Priority Alerts After Hours

Now let’s mute minor alerts at night and on weekends.
This is where Routing Rules come in.
In both teams, create a rule like:

Routing Rule: “Mute Minor Alerts Outside Hours”

• If
• Severity = minor
• Time = outside 08:00–17:00 or it’s a weekend
• Then
• Action: Mute Slack Integration

This prevents low-priority alerts from pinging Slack when no one’s around. Your monitoring stack stays active—but your team stays sane.

Final Result: Noise Down, Focus Up

With this setup, Slack becomes a sharp tool—not a firehose.

✅ Alerts are relevant
✅ Severity is respected
✅ Slack doesn’t turn into chaos

Want to try it out?
Login, start your free trial or book a quick demo and we’ll walk you through it live.

- Peer
CEO & Co-Founder of All Quiet