Event
Something that happens in a system: a log line, a metric that changes. Most of the time it is normal.
incident management
Incidents happen to everyone. What makes the difference is how we face them: calmly, in an orderly way, and willing to learn.
An incident is an unplanned event that interrupts a service or lowers its quality. Incident Management is the process that restores normal service as quickly as possible, limiting the impact on users and business.
The goal is not to never have incidents, because that is impossible. The goal is to notice early, respond well and not repeat the same mistake.
Something that happens in a system: a log line, a metric that changes. Most of the time it is normal.
An event that needs attention and notifies someone.
A real or imminent disruption that must be handled now.
The underlying cause of one or more incidents. It is studied to keep them from coming back.
The problem shows up through monitoring, an alert or a user report. Better if before the users.
You assess impact and urgency and assign a priority, which decides who is involved and how fast.
You call the right people, open a channel or ticket and name who coordinates.
First restore the service (a rollback, a restart, a move to another system), then investigate the cause.
You update colleagues, customers and managers regularly, even when the cause is still unclear.
You run a blameless review, decide concrete actions and check they get done.
In a serious incident, clear roles keep everybody from doing everything while nobody coordinates.
Coordinates, decides and keeps the big picture. Not the person who fixes it first-hand.
The technical experts who investigate and apply fixes.
Updates stakeholders and customers with clear, regular messages.
Keeps the timeline of what happens and when: gold for the final review.
It is just an example: every company defines its own levels and response times.
| Priority | Example | Typical reaction |
|---|---|---|
| P1 · Critical | The main service is down for everyone. | Everyone, right away, even at night, with continuous updates. |
| P2 · High | An important feature is degraded or down for many users. | Immediate action by the on-call person. |
| P3 · Medium | A partial problem, with a workaround. | Handled during working hours. |
| P4 · Low | A minor annoyance, with no impact on the service. | Goes to the backlog and gets planned. |
This is an introductory guide, written the way I understood things while working in the field. Every company organizes itself differently: take it as a starting point, not as a manual.