01
Log incidents the moment they surface
Create a card in Detected as soon as an alert fires or a customer reports an issue. Include the timestamp, affected service, and initial blast radius in the card description.
// Incident Response
Incidents under control.
Track every production incident from the first alert to the final post-mortem. Your on-call team gets a single source of truth when seconds matter.
Detected
3Elevated error rate on checkout API (5xx > 2%)
P0
SSL certificate expiring in 48 hours on cdn.example.com
P1
Unusual login attempts from Eastern Europe IP range
P1
Investigating
2Database connection pool exhaustion on primary replica
P0
Memory leak in background job worker after v3.8 deploy
P1
Mitigating
2Rolled back payment service to v3.7.2 - monitoring
P0
Rate limiting applied to suspicious IP block
P2
Resolved
2DNS propagation delay after provider migration
P1
Third-party email API timeout - switched to backup provider
P2
Post-mortem
2Post-mortem: March 12 payment processing outage (47 min)
P0
Post-mortem: Credential rotation triggered false alarms
P2
02
Assign severity with priority labels
Tag every incident as P0, P1, or P2. P0 means all hands on deck. Use Flux labels to filter the board by severity so your on-call team focuses on what matters most.
03
Track mitigation steps in checklists
Add a checklist to each incident card with concrete mitigation actions. Check them off as you go so the team has a live record of what has been tried and what worked.
04
Write post-mortems before closing
Move resolved incidents to Post-mortem only after documenting root cause, timeline, and follow-up actions. The card becomes a permanent record your team can reference.
01 What is an incident response board?
+
An incident response board tracks production incidents from detection through resolution and post-mortem. Each card represents an incident moving through investigation, mitigation, and review stages so nothing falls through the cracks during high-pressure situations.
02 Can I customize the severity levels?
+
Yes. Flux labels are fully customizable. You can rename P0, P1, P2 to Critical, Major, Minor or add labels like Security, Infrastructure, or Customer-Facing to match your incident classification system.
03 How does real-time sync help during incidents?
+
When an incident is active, every team member sees card updates instantly through Flux real-time sync. Move a card to Mitigating or add a checklist item, and the entire on-call team sees it without refreshing. The activity log captures every change with timestamps for your post-mortem.
// Stay prepared
Respond fast, recover faster.
No credit card. Track incidents with real-time sync so your entire team stays aligned during outages.