GuardYak Docs

How to see why a check failed in GuardYak

An alert tells you something is down; the dashboard tells you what kind of down. GuardYak shows the status code, a plain-English explanation and how long the incident has been open, so you can decide who to call.

Before you start

  • A check that has failed at least once

Plays silently with captions; the narrated version is on its way.

Transcript

When an alert arrives, see what failed, what the error means, and how long it's been happening.

Open the Dashboard. The cards at the top show how many checks are down right now, and how many incidents are open.

Under Active incidents, the failing check is listed with when it started.

In Current status, read the code and the What this means column. A five-oh-two, for example, means the web server couldn't reach the app behind it.

Steps

  1. Check the summary ▶ 0:07

    Open Dashboard. Currently down and Active incidents show the scale of the problem.

    Dashboard summary cards showing one check currently down and one active incident

  2. Find the open incident ▶ 0:16

    Under Active incidents, find the check and when the incident started.

    Active incidents panel listing the Tallyhopper client login incident

  3. Read what the error means ▶ 0:21

    In Current status, compare Status and Code, then read What this means for that row.

    Current status table with the 502 code and its plain-English explanation
ResultYou know which check is failing, the response it returned, what that response usually means and when it started.

Next steps

Updated 2026-10-26