Analyzer

The findings report. The recording is analysed for the things that usually explain a misbehaving system, and each finding is one row you can click to be taken there.

Needs: a recording.

What it finds

KIND	MEANING
Inversion	A priority inversion: a high-priority task waited on a mutex held by a lower-priority task while something in between ran
Jitter	An activation of a periodic task far off its median period
Failed op	A kernel operation that failed: a receive that timed out, a send to a full queue, a take that gave up
Verdict	A diagnosis raised by an installed Trace Domain: the domain's rules, evaluated over the recording, with the evidence listed

Each finding has a severity (error, warning, suspicious, flag, note), always shown as a coloured dot and a word, never colour alone.

Using it

The pills in the header are counts and filters at once: click inversions to see only inversions, click it again to see everything.
Click a row: the Timeline jumps to that moment with the cursor pinned and a flash, and the footer shows the full description and, for verdicts, the evidence from onset to end. Drag the footer's top edge to give it more room.
The findings are computed for the same scope as the CPU view: with Selection on there, the header carries a chip saying the report covers only that region.

Tips

Start here on an unfamiliar recording; the Timeline is much easier to read when you already know which task to watch.
A verdict's evidence lines are the domain's sampled channels at the moments that mattered, so a "queue starved" finding tells you what the queue depth and the consumer were doing, not just when.

START HERE EMAIL SUPPORT