Incident Triage
100%

Incident Response · Lesson 1

Incident Triage

Learn to turn an initial incident report into a scoped first investigation.

An initial report may say a page failed or that an alert fired. Triage means deciding what needs attention first. Write down the affected service, time, and observed behavior before choosing a response.

Reading the Report

A teammate writes this simulated report.

09:22 UTC: Visitors received 503 from the public homepage.
The staff preview still loaded during the same check.
First failure observed at approximately 09:19 UTC.

The report gives two routes and two different observations. Confirm the public homepage result and record the time and address you checked.

Which symptom should the first check focus on?

Estimating the Impact

Check how many users or requests are affected and whether the service remains usable. Determine whether the event is still happening. State uncertain estimates as estimates until you have better evidence. Use the response plan to decide whom to notify.

Which observation helps decide whether the issue is still urgent?

Choosing a Useful First Action

If the current request also fails, keep the result and look at recent service changes and logs during the affected time. A parallel healthy path helps narrow the issue. Avoid treating the first plausible explanation as confirmed cause.

The public path still fails and staff preview still works. What should you look at next?

Lesson complete

You finished Incident Triage

You can now create a focused first response to an incident report.

  • Name the affected path, time, and symptom.

  • Check current user impact.

  • Choose the next evidence source for the affected path.

Keep your learning progress

Create a free account to save this lesson and continue learning on any device.

Create a free account
Next Lesson
Back to Incident Response