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
Namespace
Google \ Cloud \ Logging \ Type
Methods
static::name
Parameter
Name
Description
value
mixed
static::value
Parameter
Name
Description
name
mixed
Constants
PBDEFAULT
Value: 0
(0) The log entry has no assigned severity level.
Generated from protobuf enum DEFAULT = 0;
DEBUG
Value: 100
(100) Debug or trace information.
Generated from protobuf enum DEBUG = 100;
INFO
Value: 200
(200) Routine information, such as ongoing status or performance.
Generated from protobuf enum INFO = 200;
NOTICE
Value: 300
(300) Normal but significant events, such as start up, shut down, or
a configuration change.
Generated from protobuf enum NOTICE = 300;
WARNING
Value: 400
(400) Warning events might cause problems.
Generated from protobuf enum WARNING = 400;
ERROR
Value: 500
(500) Error events are likely to cause problems.
Generated from protobuf enum ERROR = 500;
CRITICAL
Value: 600
(600) Critical events cause more severe problems or outages.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Google API Common Protos Client - Class LogSeverity (4.12.3)\n\nVersion latestkeyboard_arrow_down\n\n- [4.12.3 (latest)](/php/docs/reference/common-protos/latest/Cloud.Logging.Type.LogSeverity)\n- [4.12.2](/php/docs/reference/common-protos/4.12.2/Cloud.Logging.Type.LogSeverity)\n- [4.11.0](/php/docs/reference/common-protos/4.11.0/Cloud.Logging.Type.LogSeverity)\n- [4.10.0](/php/docs/reference/common-protos/4.10.0/Cloud.Logging.Type.LogSeverity)\n- [4.9.0](/php/docs/reference/common-protos/4.9.0/Cloud.Logging.Type.LogSeverity)\n- [4.8.3](/php/docs/reference/common-protos/4.8.3/Cloud.Logging.Type.LogSeverity) \nReference documentation and code samples for the Google API Common Protos Client class LogSeverity.\n\nThe severity of the event described in a log entry, expressed as one of the\nstandard severity levels listed below. For your reference, the levels are\nassigned the listed numeric values. The effect of using numeric values other\nthan those listed is undefined.\n\nYou can filter for log entries by severity. For example, the following\nfilter expression will match log entries with severities `INFO`, `NOTICE`,\nand `WARNING`:\nseverity \\\u003e DEBUG AND severity \\\u003c= WARNING\nIf you are writing log entries, you should map other severity encodings to\none of these standard levels. For example, you might map all of Java's FINE,\nFINER, and FINEST levels to `LogSeverity.DEBUG`. You can preserve the\noriginal severity level in the log entry payload if you wish.\n\nProtobuf type `google.logging.type.LogSeverity`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ Logging \\\\ Type\n\nMethods\n-------\n\n### static::name\n\n### static::value\n\nConstants\n---------\n\n### PBDEFAULT\n\n Value: 0\n\n(0) The log entry has no assigned severity level.\n\nGenerated from protobuf enum `DEFAULT = 0;`\n\n### DEBUG\n\n Value: 100\n\n(100) Debug or trace information.\n\nGenerated from protobuf enum `DEBUG = 100;`\n\n### INFO\n\n Value: 200\n\n(200) Routine information, such as ongoing status or performance.\n\nGenerated from protobuf enum `INFO = 200;`\n\n### NOTICE\n\n Value: 300\n\n(300) Normal but significant events, such as start up, shut down, or\na configuration change.\n\nGenerated from protobuf enum `NOTICE = 300;`\n\n### WARNING\n\n Value: 400\n\n(400) Warning events might cause problems.\n\nGenerated from protobuf enum `WARNING = 400;`\n\n### ERROR\n\n Value: 500\n\n(500) Error events are likely to cause problems.\n\nGenerated from protobuf enum `ERROR = 500;`\n\n### CRITICAL\n\n Value: 600\n\n(600) Critical events cause more severe problems or outages.\n\nGenerated from protobuf enum `CRITICAL = 600;`\n\n### ALERT\n\n Value: 700\n\n(700) A person must take an action immediately.\n\nGenerated from protobuf enum `ALERT = 700;`\n\n### EMERGENCY\n\n Value: 800\n\n(800) One or more systems are unusable.\n\nGenerated from protobuf enum `EMERGENCY = 800;`"]]
