package google.logging.type

Get desktop application:
View/edit binary Protocol Buffers messages

A common proto for logging HTTP requests.

Used in: v2.LogEntry

• string request_method = 1

  The request method. Examples: `"GET"`, `"HEAD"`, `"PUT"`, `"POST"`.

• string request_url = 2

  The scheme (http, https), the host name, the path and the query portion of the URL that was requested. Example: `"http://example.com/some/info?color=red"`.

• int64 request_size = 3

  The size of the HTTP request message in bytes, including the request headers and the request body.

• int32 status = 4

  The response code indicating the status of response. Examples: 200, 404.

• int64 response_size = 5

  The size of the HTTP response message sent back to the client, in bytes, including the response headers and the response body.

• string user_agent = 6

  The user agent sent by the client. Example: `"Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Q312461; .NET CLR 1.0.3705)"`.

• string remote_ip = 7

  The IP address (IPv4 or IPv6) of the client that issued the HTTP request. Examples: `"192.168.1.1"`, `"FE80::0202:B3FF:FE1E:8329"`.

• string referer = 8

  The referer URL of the request, as defined in [HTTP/1.1 Header Field Definitions](http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html).

• bool cache_hit = 9

  Whether or not an entity was served from cache (with or without validation).

• bool validated_with_origin_server = 10

  Whether or not the response was validated with the origin server before being served from cache. This field is only meaningful if `cache_hit` is True.

The severity of the event described in a log entry. These guideline severity levels are ordered, with numerically smaller levels treated as less severe than numerically larger levels. If the source of the log entries uses a different set of severity levels, the client should select the closest corresponding `LogSeverity` value. For example, Java's FINE, FINER, and FINEST levels might all map to `LogSeverity.DEBUG`. If the original severity code must be preserved, it can be stored in the payload.

Used in: v2.LogEntry

• 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 configuration.

• 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 brief outages.

• ALERT = 700

  A person must take an action immediately.

• EMERGENCY = 800

  One or more systems are unusable.