New in this Version

allquiet_routing - new routing conditions

• labels (List of String) Labels that must appear on the routing team and/or the source integration of the incident. Use labels_match_type to require all listed labels (AND) or any one (OR).

• labels_match_type (String) How labels are combined when multiple are set. Possible values are: all, any

We updated our routing rules to include Labels as a conditional filter. This update allows you to route incidents based on specific labels assigned to your integrations or teams.

How it works

You can now require specific labels to trigger a routing rule. All Quiet evaluates these labels against the source integration and the target routing team. If you disable this filter, the rule remains eligible for all incidents by default.

Key Configuration Options

Why this matters

• Reduced Noise: Ensure only relevant incidents alert specific sub-teams.

• Granular Control: Use labels like production to separate high-priority traffic from routine background tasks.

• Scalability: Manage complex routing logic across large organizations without creating dozens of separate integrations.

Technical Fact: All Quiet's label-based routing supports boolean logic (AND/OR). It validates labels against two entities: the integration that ingested the incident and the team assigned to handle it. This creates a multi-layered filter for precise incident distribution.

Our new StatusCake integration connects your external availability signals directly to All Quiet. You can now sync uptime checks with your existing incident management workflows to reduce MTTR and eliminate monitoring silos.

Key Benefits for On-Call Teams

• Automated Incident Creation: All Quiet converts StatusCake check failures into incidents immediately.

• Contextual Triage: Each incident includes specific details from StatusCake. This helps your team identify outages without switching between tools.

• Organizational Alignment: Map StatusCake alerts to specific All Quiet organizations and teams. This ensures the right people receive the notification.

• Unified Reliability Tracking: Track outages and degradations in one central place where your team already works.

How it works

1. Connect: Link your StatusCake account to your All Quiet webhook(s).

2. Map: Assign StatusCake checks to your preferred All Quiet teams.

3. Resolve: Receive alerts for downtime, triage the incident with clear context, and restore services faster.

Here’s how to set up you StatusCake integration with All Quiet in minutes.

New in this Version:

• allquiet_integration

  • HTTP Monitors - Optional Attribute ignore_non_http_errors (Boolean):
    When true, connection and transport failures (non-HTTP errors) are ignored and do not trigger incidents

• allquiet_integration

  • Optional Attribute labels (List of String):
    Labels applied to the integration for filtering and organization

We added labels to the integration level. You can now manage labels for each integration, similar to how you use team labels.

Why this update matters

Effective incident management requires fast context. Integration-level labels attach metadata to incidents at the source. This helps your team understand the category of an incident before triage begins.

What is new

• Integration labels: Create and manage labels within each integration.

• Consistent experience: Use the label system you already know from teams.

• Layered metadata: Keep team-level labels for shared defaults. Use integration-level labels for source-specific data.

The benefits

• Faster classification: Classify incoming incidents automatically.

• Better consistency: All incidents from the same integration carry identical metadata.

Integration-level labels give you control where incidents begin.

All Quiet now integrates with Mattermost 🎉

Benefit from the flexible two-way integration

Send All Quiet incidents to your very own Mattermost servers
Benefit from secure collaboration on your sovereign infrastructure. Deploy anywhere, control everything. Trusted by governments, enterprises and militaries around the world.

Create new incidents directly from Mattermost
Use custom slash commands to trigger All Quiet incidents and escalations from your Mattermost channels. Team members can then assign, affect services, comment, and resolve incidents without leaving Mattermost.

Here’s how to ➡ set up everything in minutes.

New in this Version:

• allquiet_integration

  • HTTP Monitors - Optional Attribute override_accepted_status_codes (List of Number). If empty, 2xx status codes are accepted. If specified, only the specified HTTP status codes are considered 'up' (e.g. 200, 201, 204, 302). Each value must be between 100 and 599.

• allquiet_team_escalations

  • Optional Attribute auto_assign_to_teams_repeat_alerts (Boolean) - Default: true

    • If true, notify all on-call users when auto-assigning to teams (including those previously notified).

    • If false, only newly assigned teams are notified.

• allquiet_routing

  • Optional Attribute assign_to_teams_repeat_alerts (Boolean) - Default: true

    • If true, notify all assigned users and teams, including those previously notified.

    • If false, only newly assigned users / teams are notified.

• allquiet_services

  • Optional Attribute integrations (Attributes List): Link integrations to this service. Each entry links an integration to the service with optional severity filter. Incident from this integration will, if severity matches, auto affect this service

We’ve added new report views at Inbound Integration, Team and Organization level, giving you clearer insight into alert volume, response performance, and trends across your whole setup.

These reports make it easier to compare teams, track improvements over time, and identify where to focus your reliability efforts.

Learn more about the new reports in our documentation.