All Quiet changelog
New: Label-Based Routing for Precise Incident Orchestration
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
Feature | Function |
Match All (AND) | The incident must carry every listed label to trigger the rule. |
Match Any (OR) | Any single label from your list will trigger the rule. |
Source Alignment | Matches labels from the source integration and/or the routing team. |
Why this matters
Reduced Noise: Ensure only relevant incidents alert specific sub-teams.
Granular Control: Use labels like
productionto 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.