A common proto for logging HTTP requests. Only contains semantics
defined by the HTTP specification. Product-specific logging
information MUST be defined in a separate message.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["This document details the Google.Cloud.Logging.Type library, with version 3.4.0 as the current context, and provides links to other available versions, including the latest at 4.2.0."],["The library includes a class named `HttpRequest`, which is designed for logging HTTP requests and adheres strictly to the HTTP specification."],["The document describes an enum, `LogSeverity`, which defines the severity levels of log entries and offers guidance on filtering logs by severity."],["The documentation outlines how to map other severity encodings, such as Java's FINE levels, to the standard `LogSeverity` levels for consistency."]]],[]]
