Index
HttpRequest
(message)LogSeverity
(enum)
HttpRequest
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.
Fields | |
---|---|
request_method |
The request method. Examples: |
request_url |
The scheme (http, https), the host name, the path and the query portion of the URL that was requested. Example: |
request_size |
The size of the HTTP request message in bytes, including the request headers and the request body. |
status |
The response code indicating the status of response. Examples: 200, 404. |
response_size |
The size of the HTTP response message sent back to the client, in bytes, including the response headers and the response body. |
user_agent |
The user agent sent by the client. Example: |
remote_ip |
The IP address (IPv4 or IPv6) of the client that issued the HTTP request. This field can include port information. Examples: |
server_ip |
The IP address (IPv4 or IPv6) of the origin server that the request was sent to. This field can include port information. Examples: |
referer |
The referer URL of the request, as defined in HTTP/1.1 Header Field Definitions. |
latency |
The request processing latency on the server, from the time the request was received until the response was sent. For WebSocket connections, this field refers to the entire time duration of the connection. |
cache_lookup |
Whether or not a cache lookup was attempted. |
cache_hit |
Whether or not an entity was served from cache (with or without validation). |
cache_validated_with_origin_server |
Whether or not the response was validated with the origin server before being served from cache. This field is only meaningful if |
cache_fill_bytes |
The number of HTTP response bytes inserted into cache. Set only when a cache fill was attempted. |
protocol |
Protocol used for the request. Examples: "HTTP/1.1", "HTTP/2" |
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.
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. |
ALERT |
(700) A person must take an action immediately. |
EMERGENCY |
(800) One or more systems are unusable. |