5 min leitura • Guide 653 of 877
How to Use GitScrum for Developer On-Call Rotations?
How to use GitScrum for developer on-call rotations?
Manage on-call rotations in GitScrum with rotation schedules, incident tracking, and handoff documentation in NoteVault. Track on-call load, coordinate escalations, improve runbooks. On-call teams with structured workflow reduce alert fatigue by 40% [Source: On-Call Research 2024].
On-call workflow:
- Alert - Notification received
- Assess - Evaluate severity
- Respond - Take action
- Resolve - Fix issue
- Document - Log incident
- Follow-up - Prevention tasks
- Handoff - Next rotation
On-call labels
| Label | Purpose |
|---|---|
| type-incident | On-call incident |
| oncall-active | During rotation |
| alert-noisy | Needs improvement |
| alert-actionable | Valid alert |
| needs-runbook | Documentation needed |
| escalated | Was escalated |
On-call columns
| Column | Purpose |
|---|---|
| Active Incidents | Current issues |
| Investigating | Being worked |
| Resolved | Fixed |
| Follow-up | Post-incident |
| Improvements | Alert/runbook work |
NoteVault on-call docs
| Document | Content |
|---|---|
| On-call schedule | Rotation calendar |
| Runbooks | Response procedures |
| Escalation matrix | Who to contact |
| Handoff template | What to pass on |
| Alert catalog | All alerts explained |
Incident task template
## Incident: [alert name/description]
### Details
- Triggered: [time]
- Severity: [level]
- Service: [affected]
- On-call: [@person]
### Response
- Time to acknowledge: [minutes]
- Time to resolve: [minutes]
- Actions taken: [description]
### Resolution
[What fixed it]
### Root Cause
[Why it happened]
### Follow-up
- [ ] Update runbook
- [ ] Fix root cause
- [ ] Improve alerting
Rotation schedule
| Week | Primary | Secondary |
|---|---|---|
| Week 1 | @Alice | @Bob |
| Week 2 | @Bob | @Charlie |
| Week 3 | @Charlie | @Dana |
| Week 4 | @Dana | @Alice |
Handoff template
## On-Call Handoff: [date]
### Outgoing: @[name]
### Incoming: @[name]
### Active Issues
- [Issue 1]: [status]
- [Issue 2]: [status]
### Incidents This Rotation
| Time | Alert | Resolution |
|------|-------|------------|
| [time] | [alert] | [fix] |
### Heads Up
- [Thing to watch out for]
- [Scheduled maintenance]
### Improvement Suggestions
- [Noisy alert to fix]
- [Runbook to update]
Alert classification
| Type | Action |
|---|---|
| Actionable | Response needed |
| Warning | Monitor |
| Noisy | Improve or remove |
| Missing | Need to add |
On-call metrics
| Metric | Track |
|---|---|
| Incidents per rotation | Load distribution |
| Time to acknowledge | Response speed |
| Time to resolve | Resolution efficiency |
| Pages outside hours | After-hours burden |
| Noisy alert ratio | Alert quality |
Improving alert quality
| Issue | Task |
|---|---|
| Too many alerts | Tune thresholds |
| Not actionable | Improve or remove |
| Missing context | Add runbook link |
| Wrong routing | Fix routing rules |
Runbook structure
## Runbook: [alert name]
### Alert Description
[What this alert means]
### Severity
[How urgent is this]
### First Steps
1. [Step 1]
2. [Step 2]
3. [Step 3]
### Common Causes
| Symptom | Cause | Fix |
|---------|-------|-----|
| [symptom] | [cause] | [action] |
### Escalation
- When: [escalation criteria]
- Who: [escalation path]
### Recent Changes
[Link to relevant deployments]
Fair rotation practices
| Practice | Implementation |
|---|---|
| Even distribution | Track pages per person |
| Swap flexibility | Process for swaps |
| Comp time | After heavy rotations |
| Holiday coverage | Special handling |
Common on-call issues
| Issue | Solution |
|---|---|
| Alert fatigue | Improve alert quality |
| Missing runbooks | Documentation tasks |
| Uneven load | Fair rotation |
| Poor handoffs | Structured handoff |
On-call retrospective
| Question | Discussion |
|---|---|
| Busiest incidents? | What consumed time |
| Noisy alerts? | What to improve |
| Missing runbooks? | What to document |
| Process issues? | What to change |