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.
[[["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,["# Cloud Logging V2 API - Module Google::Cloud::Logging::Type::LogSeverity (v1.3.0)\n\nVersion latestkeyboard_arrow_down\n\n- [1.3.0 (latest)](/ruby/docs/reference/google-cloud-logging-v2/latest/Google-Cloud-Logging-Type-LogSeverity)\n- [1.2.1](/ruby/docs/reference/google-cloud-logging-v2/1.2.1/Google-Cloud-Logging-Type-LogSeverity)\n- [1.1.0](/ruby/docs/reference/google-cloud-logging-v2/1.1.0/Google-Cloud-Logging-Type-LogSeverity)\n- [1.0.1](/ruby/docs/reference/google-cloud-logging-v2/1.0.1/Google-Cloud-Logging-Type-LogSeverity)\n- [0.13.0](/ruby/docs/reference/google-cloud-logging-v2/0.13.0/Google-Cloud-Logging-Type-LogSeverity)\n- [0.12.2](/ruby/docs/reference/google-cloud-logging-v2/0.12.2/Google-Cloud-Logging-Type-LogSeverity)\n- [0.11.0](/ruby/docs/reference/google-cloud-logging-v2/0.11.0/Google-Cloud-Logging-Type-LogSeverity)\n- [0.10.1](/ruby/docs/reference/google-cloud-logging-v2/0.10.1/Google-Cloud-Logging-Type-LogSeverity)\n- [0.9.0](/ruby/docs/reference/google-cloud-logging-v2/0.9.0/Google-Cloud-Logging-Type-LogSeverity)\n- [0.8.1](/ruby/docs/reference/google-cloud-logging-v2/0.8.1/Google-Cloud-Logging-Type-LogSeverity)\n- [0.7.0](/ruby/docs/reference/google-cloud-logging-v2/0.7.0/Google-Cloud-Logging-Type-LogSeverity)\n- [0.6.0](/ruby/docs/reference/google-cloud-logging-v2/0.6.0/Google-Cloud-Logging-Type-LogSeverity)\n- [0.5.6](/ruby/docs/reference/google-cloud-logging-v2/0.5.6/Google-Cloud-Logging-Type-LogSeverity) \nReference documentation and code samples for the Cloud Logging V2 API module Google::Cloud::Logging::Type::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\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`: \n\n severity \u003e DEBUG AND severity \u003c= WARNING\n\n\u003cbr /\u003e\n\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\nConstants\n---------\n\n### DEFAULT\n\n**value:** 0 \n(0) The log entry has no assigned severity level.\n\n### DEBUG\n\n**value:** 100 \n(100) Debug or trace information.\n\n### INFO\n\n**value:** 200 \n(200) Routine information, such as ongoing status or performance.\n\n### NOTICE\n\n**value:** 300 \n(300) Normal but significant events, such as start up, shut down, or\na configuration change.\n\n### WARNING\n\n**value:** 400 \n(400) Warning events might cause problems.\n\n### ERROR\n\n**value:** 500 \n(500) Error events are likely to cause problems.\n\n### CRITICAL\n\n**value:** 600 \n(600) Critical events cause more severe problems or outages.\n\n### ALERT\n\n**value:** 700 \n(700) A person must take an action immediately.\n\n### EMERGENCY\n\n**value:** 800 \n(800) One or more systems are unusable."]]