Package-Level Type Names (total 2, both are exported)
/* sort exporteds by: | */
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 number of HTTP response bytes inserted into cache. Set only when a
cache fill was attempted.
Whether or not an entity was served from cache
(with or without validation).
Whether or not a cache lookup was attempted.
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 request processing latency on the server, from the time the request was
received until the response was sent.
Protocol used for the request. Examples: "HTTP/1.1", "HTTP/2", "websocket"
The referer URL of the request, as defined in
[HTTP/1.1 Header Field
Definitions](http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html).
The IP address (IPv4 or IPv6) of the client that issued the HTTP
request. This field can include port information. Examples:
`"192.168.1.1"`, `"10.0.0.1:80"`, `"FE80::0202:B3FF:FE1E:8329"`.
The request method. Examples: `"GET"`, `"HEAD"`, `"PUT"`, `"POST"`.
The size of the HTTP request message in bytes, including the request
headers and the request body.
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"`.
The size of the HTTP response message sent back to the client, in bytes,
including the response headers and the response body.
The IP address (IPv4 or IPv6) of the origin server that the request was
sent to. This field can include port information. Examples:
`"192.168.1.1"`, `"10.0.0.1:80"`, `"FE80::0202:B3FF:FE1E:8329"`.
The response code indicating the status of response.
Examples: 200, 404.
The user agent sent by the client. Example:
`"Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Q312461; .NET
CLR 1.0.3705)"`.
sizeCacheprotoimpl.SizeCachestateprotoimpl.MessageStateunknownFieldsprotoimpl.UnknownFields
Deprecated: Use HttpRequest.ProtoReflect.Descriptor instead.
(*T) GetCacheFillBytes() int64(*T) GetCacheHit() bool(*T) GetCacheLookup() bool(*T) GetCacheValidatedWithOriginServer() bool(*T) GetLatency() *durationpb.Duration(*T) GetProtocol() string(*T) GetReferer() string(*T) GetRemoteIp() string(*T) GetRequestMethod() string(*T) GetRequestSize() int64(*T) GetRequestUrl() string(*T) GetResponseSize() int64(*T) GetServerIp() string(*T) GetStatus() int32(*T) GetUserAgent() string(*T) ProtoMessage()(*T) ProtoReflect() protoreflect.Message(*T) Reset()(*T) String() string
*T : google.golang.org/protobuf/reflect/protoreflect.ProtoMessage
*T : google.golang.org/protobuf/runtime/protoiface.MessageV1
*T : fmt.Stringer
*T : google.golang.org/protobuf/internal/impl.messageV1
*T : context.stringer
*T : os/signal.stringer
*T : runtime.stringer
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.
( T) Descriptor() protoreflect.EnumDescriptor( T) Enum() *LogSeverity
Deprecated: Use LogSeverity.Descriptor instead.
( T) Number() protoreflect.EnumNumber( T) String() string( T) Type() protoreflect.EnumType
T : google.golang.org/protobuf/reflect/protoreflect.Enum
T : fmt.Stringer
T : google.golang.org/protobuf/internal/impl.enumV1
T : context.stringer
T : os/signal.stringer
T : runtime.stringer
func LogSeverity.Enum() *LogSeverity
const LogSeverity_ALERT
const LogSeverity_CRITICAL
const LogSeverity_DEBUG
const LogSeverity_DEFAULT
const LogSeverity_EMERGENCY
const LogSeverity_ERROR
const LogSeverity_INFO
const LogSeverity_NOTICE
const LogSeverity_WARNING
Package-Level Functions (total 6, none are exported)
Package-Level Constants (total 9, all are exported)
(700) A person must take an action immediately.
(600) Critical events cause more severe problems or outages.
(100) Debug or trace information.
(0) The log entry has no assigned severity level.
(800) One or more systems are unusable.
(500) Error events are likely to cause problems.
(200) Routine information, such as ongoing status or performance.
(300) Normal but significant events, such as start up, shut down, or
a configuration change.
(400) Warning events might cause problems.
The pages are generated with Goldsv0.3.2. (GOOS=linux GOARCH=amd64)
Golds is a Go 101 project developed by Tapir Liu.
PR and bug reports are welcome and can be submitted to the issue list.
Please follow @Go100and1 (reachable from the left QR code) to get the latest news of Golds.