Cloud Logging V2 API - Module Google::Cloud::Logging::Type::LogSeverity (v0.11.0)

Reference documentation and code samples for the Cloud Logging V2 API module Google::Cloud::Logging::Type::LogSeverity.

The severity of the event described in a log entry, expressed as one of the standard severity levels listed below. For your reference, the levels are assigned the listed numeric values. The effect of using numeric values other than those listed is undefined.

You can filter for log entries by severity. For example, the following filter expression will match log entries with severities INFO, NOTICE, and WARNING:

severity > DEBUG AND severity <= WARNING

If you are writing log entries, you should map other severity encodings to one of these standard levels. For example, you might map all of Java's FINE, FINER, and FINEST levels to LogSeverity.DEBUG. You can preserve the original severity level in the log entry payload if you wish.

Constants

DEFAULT

value: 0
(0) The log entry has no assigned severity level.

DEBUG

value: 100
(100) Debug or trace information.

INFO

value: 200
(200) Routine information, such as ongoing status or performance.

NOTICE

value: 300
(300) Normal but significant events, such as start up, shut down, or a configuration change.

WARNING

value: 400
(400) Warning events might cause problems.

ERROR

value: 500
(500) Error events are likely to cause problems.

CRITICAL

value: 600
(600) Critical events cause more severe problems or outages.

ALERT

value: 700
(700) A person must take an action immediately.

EMERGENCY

value: 800
(800) One or more systems are unusable.