Google API Common Protos Client - Class LogSeverity (4.8.3)

Reference documentation and code samples for the Google API Common Protos Client class 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.

Protobuf type google.logging.type.LogSeverity

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

Generated from protobuf enum DEFAULT = 0;

(100) Debug or trace information.

Generated from protobuf enum DEBUG = 100;

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

Generated from protobuf enum INFO = 200;

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

Generated from protobuf enum NOTICE = 300;

(400) Warning events might cause problems.

Generated from protobuf enum WARNING = 400;

(500) Error events are likely to cause problems.

Generated from protobuf enum ERROR = 500;

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

Generated from protobuf enum CRITICAL = 600;

(700) A person must take an action immediately.

Generated from protobuf enum ALERT = 700;

(800) One or more systems are unusable.

Generated from protobuf enum EMERGENCY = 800;