Enum LogLevel
Represents the severity levels used for logging messages. Levels are ordered from lowest
to highest severity. Log receivers use these values to set their label threshold via
LogLabelLevel, and the static FilterLevel field uses them to suppress
messages below a chosen severity.
Assembly: ScyllaCore.dll
Syntax
Fields
| Name |
Description |
| Debug |
Detailed debugging information (1). Used for developer-facing diagnostics that
are useful during development and testing but should not appear in production logs. Like
Trace, all Debug(object, string, int) calls are conditionally
compiled with the DEBUG symbol and are stripped from release builds entirely.
|
| Error |
Critical error (6). Indicates that a serious failure occurred that may have caused
incorrect behavior or data loss, but has not yet stopped the application. Errors should be
investigated and resolved; they represent conditions that are not expected in a healthy system.
|
| Fatal |
Terminal error (7). Indicates an unrecoverable failure that is expected to halt or
severely degrade the application. A fatal message signals that continued execution is unsafe
or impossible and that the application should be shut down or restarted.
|
| Info |
General informational output (3). Suitable for production logs that confirm normal
application behavior, such as successful initialization, configuration loading, or state
transitions. Use this level for messages that remain useful to operators after release.
|
| Maximum |
A special sentinel ceiling value (999). When FilterLevel is set to
Maximum, no messages pass the filter (not even Fatal), effectively
disabling all level-filtered logging. Log receivers that set their LogLabelLevel to
Maximum will never prepend a label to any message.
|
| Minimum |
A special sentinel floor value (-1). Any message logged at or above this level
always passes the filter check. Log receivers that set their LogLabelLevel to
Minimum will prepend a label to every message regardless of its severity.
|
| Notice |
Prominent informational output (4). A step above Info in visibility
but below Warning in severity. Use this for events that are noteworthy -
such as significant state changes or milestones - but do not represent a problem. Not a
warning, not an error; simply information that deserves extra attention.
|
| System |
Framework-internal system messages (2). Reserved for messages emitted by Scylla's
own infrastructure (module lifecycle, initialization, subsystem events). This level bypasses
the FilterLevel check and is always delivered when logging is enabled,
making it suitable for critical framework status output that must never be silenced.
|
| Trace |
Temporary debugging trace output (0). Intended for short-lived instrumentation
such as inspecting a single property or confirming a code path is reached during active
development. All calls to Trace(object, string, int) are conditionally
compiled with the DEBUG symbol and produce zero runtime overhead in release builds.
|
| Warning |
Non-critical problem notification (5). Indicates that something unexpected occurred
but the application can continue operating normally. Use this for recoverable anomalies,
deprecated-API usage, missing optional resources, or degraded-mode operation.
|