Description
Alert deduplication uses placeholders for severity and bridge resolution. backend/src/services/alertDeduplication.service.ts:60 marks the incident status update as a "placeholder for severity update", and :69 sets bridgeId: "unknown" with a "placeholder" comment. Related incidents are not enriched with correct severity or bridge context.
Requirements and context
- Derive and apply the correct severity when correlating duplicate alerts
- Resolve the actual bridge id for correlated incidents instead of "unknown"
- Preserve existing deduplication behavior
- Add tests covering severity derivation and bridge resolution
Suggested execution
Fork the repo and create a branch
git checkout -b feature/service-alert-dedup-severity-bridge
Implement changes
- Replace severity-update placeholder with real derivation
- Resolve bridge id from alert context
- Add comprehensive tests
Example commit message
feat: implement alert deduplication severity and bridge resolution
Guidelines
- Assignment required before starting
- PR must include a closing reference to this issue
- Timeframe: 72 hours
Description
Alert deduplication uses placeholders for severity and bridge resolution.
backend/src/services/alertDeduplication.service.ts:60marks the incident status update as a "placeholder for severity update", and:69setsbridgeId: "unknown"with a "placeholder" comment. Related incidents are not enriched with correct severity or bridge context.Requirements and context
Suggested execution
Fork the repo and create a branch
Implement changes
Example commit message
Guidelines