Skip to content

std:logging/Level

Canonical occurrence: protos/lib/logging/Level.protos · Protos revision: e99b712ecf658a527b1fe82c8beba2c1286d8dc9.

Canonical logging severity levels. The five levels, in ascending order of severity, are TRACE, DEBUG, INFO, WARN, and ERROR. Each level is its canonical String value: Level.INFO is exactly "INFO", so a level is immutable, compares with === and ==, and keeps its identity across Actor, Task, and Process boundaries without any shared registry.

There is no FATAL level: logging reports severity and never implies terminating a Process. Severity order is observed only through compare; no numeric rank is part of the public contract.

This page lists the complete mechanically observable top-level slot inventory required by D067. Authored documentation, when present, is canonical D062 prose; mechanical presence alone does not create a stability or compatibility promise.

Detailed diagnostics intended for debugging.

No callable shape is mechanically recorded for this slot.

A failure of the operation being reported.

No callable shape is mechanically recorded for this slot.

Ordinary operational information.

No callable shape is mechanically recorded for this slot.

The finest-grained diagnostic level.

No callable shape is mechanically recorded for this slot.

A condition that deserves attention but does not prevent progress.

No callable shape is mechanically recorded for this slot.

Answers -1, 0, or 1 as level left is less severe than, equal to, or more severe than level right. Both arguments must be canonical levels; any other value signals an Error. Arguments are recognized by String identity only, so no behavior of an argument is invoked.

Exact module source · Standard-library API · Standard library overview