Get desktop application:
View/edit binary Protocol Buffers messages
One value. A cell with no value set is a missing value (rendered as null).
Used in:
Used in:
What the values are measured in ("bytes", "percent", ...); empty when nothing.
Used in:
Seconds since the unix epoch, carried in a cell's `i`.
Used in: ,
Set by a producer whose whole fetch failed. The core then reports each section that producer returned last time with this error.
Reading the latest snapshot. Consumer (REST, the `nscp test` console, a module) -> core, through NSAPIDiagnosticsQuery. Never triggers a collection: the answer is the snapshot the last round left.
Used in:
Only this section (empty for all of them).
Used in:
Whether diagnostics are collected at all ([/settings/core/failed checks] capture diagnostics).
The snapshot's id, monotonic for the lifetime of the process; 0 when there is none yet (the first round has not run).
When the core finished the round, seconds since the unix epoch.
The sections asked for: all of them, or the one named in the request (none when the snapshot does not have it).
The row cap in force (`diagnostics rows`).
Section names `prune pattern` left out of the snapshot.
Sections dropped because the snapshot already held the most it may (16) or one of the same name.
The cells of one row, in column order. The builder makes every row exactly as wide as the section has columns.
Used in:
Used in:
Dotted and lower case: "processes.top_cpu", "failures.recent".
The module that produced it (set by the core), or "core".
When the producer took the data, seconds since the unix epoch. Per section: a snapshot can hold a process table one second old next to a directory walk ten minutes old.
A row, cell or size cap cut it: "10 rows" is then "at least 10".
Set when the section could not be collected, or not all of it: a producer that reads several sources (two event logs) reports the one that failed here and still carries the rows from the others. A section that failed and one that is absent mean different things to a reader.