Rules Engine
Define routing rules, severity overrides, and auto-assignment with YAML-based configuration. Version-controlled and fully auditable. PMs configure routing. EMs set severity policies. Developers focus on code.
YAML Configuration
Rules are defined in plain YAML files that live alongside your code. Review in PRs, track in git, deploy with confidence.
Human-Readable
No proprietary DSL. Anyone on the team can read and write routing rules in familiar YAML syntax.
Version-Controlled
Store rules in git. Review changes in pull requests. Roll back instantly if a rule causes issues.
Schema Validated
The CLI validates rules before apply. Catch syntax errors and invalid references before they hit production.
Routing Rules
Control where signals go based on source, severity, tags, service name, or any metadata field.
- ✓ Match on any signal field
- ✓ Regex and glob pattern support
- ✓ Fallback and catch-all rules
- ✓ Multi-destination routing
Severity Overrides
Override AI-assigned severity based on business context. Ensure critical services always get high-priority treatment.
- ✓ Boost severity for production services
- ✓ Suppress noise from staging
- ✓ Time-based rules (on-call hours)
- ✓ Per-team severity thresholds
Auto-Assignment
Map services to teams, define on-call rotations, and let the rules engine assign tickets to the right people every time.
- ✓ Service-to-team ownership maps
- ✓ On-call rotation integration
- ✓ Load-balanced assignment
Audit Trail
Every rule evaluation is logged. See exactly why a signal was routed, assigned, or escalated for full transparency.
- ✓ Complete decision logs
- ✓ Rule change history
- ✓ Exportable for compliance
What This Means For Your Team
For PMs
Route signal types to different backlogs. CVEs to security reviews. Error spikes to on-call.
For EMs
Set severity overrides for production. Suppress staging noise. Full audit trail for compliance.
For Developers
Tickets route to the right team automatically. No more re-assignments.
Take Control of Signal Routing
Define your rules in YAML, version them in git, and let SignalManager enforce them automatically.