Stay organized with collections
Save and categorize content based on your preferences.
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.
Enums
DEFAULT
(0) The log entry has no assigned severity level.
DEBUG
(100) Debug or trace information.
INFO
(200) Routine information, such as ongoing status or performance.
NOTICE
(300) Normal but significant events, such as start up, shut down, or a configuration change.
WARNING
(400) Warning events might cause problems.
ERROR
(500) Error events are likely to cause problems.
CRITICAL
(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-06-30 UTC."],[],[],null,["# LogSeverity\n\nThe 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.\n\nYou can filter for log entries by severity. For example, the following filter expression will match log entries with severities `INFO`, `NOTICE`, and `WARNING`: \n\n severity \u003e DEBUG AND severity \u003c= WARNING\n\nIf 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."]]
