Opišite svojo vlogo v produkcijskem incidentu.

Question

Accepted Answer

Želijo videti, da ostaneš **miren, metodičen in brez krivde** pod pritiskom — najprej obnoviti storitev, drugič diagnosticirati, tretjič pa preprečiti ponovitev. Uporabi **STAR**.

## Kako se lotiti

```text
INCIDENT ORDER
1. Stabilize — stop the bleeding (rollback, failover, mitigate)
2. Communicate — keep stakeholders updated on a clear channel
3. Diagnose — root cause once it's stable, not during
4. Prevent — a blameless post-mortem with action items
```

## Obdelan primer

```text
S: A deploy caused checkout errors for ~15% of users.
T: I was on call and had to restore service fast.
A: I rolled back the deploy first (service recovered in minutes), posted updates
   every 10 minutes, then traced the cause to an unhandled null from a new API
   field. I added a guard and a contract test.
R: Downtime stayed under 20 minutes. The post-mortem added the missing test to
   CI so it can't recur.
```

## Dobro v primerjavi s šibkim

```text
✓ Mitigate first, communicate, blameless follow-up
✗ Debugging live while users are down
✗ Blaming the person who deployed
```

## Zakaj je to pomembno

Incidenti testirajo mirnost — ekipa potrebuje stabilne roke, ne panike, ko so stvari pokvarjene.

Nabor brez krivde ljudi drži poštenimi glede vzrokov, kar je edini način, da dejansko preprečiš ponovitve.

To, kako se obneseš v najslabšem dnevu, pove več o tvoji seniornosti kot to, kako se obneseš v dobrih dneh.