Proxy Log Fields
editProxy Log Fields
editThese fields are subject to change, though the vast majority of them are generic for HTTP requests and should be relatively stable.
Field |
Description |
|
the IP on the connection, i.e. a proxy IP if the request has been proxied |
|
the time the request was returned in ms since unix epoch |
|
the HTTP status returned to the client |
|
the product instance name the request was forwarded to |
|
the allocator IP address the request was forwarded to |
|
the length of the request body, a value of |
|
the request path from the url |
|
the total capacity of the handling instance |
|
the total time taken for the request in milliseconds |
|
the authenticated user for the request (only supported for basic authentication) |
|
the total capacity of the handling cluster |
|
the |
|
the client IP for the request (may differ from proxy ip if |
|
the number of availablity zones supported by the target cluster |
|
the number of bytes written in the response body |
|
a unique ID represented a single client connecition, multiple requests may use a single connection |
|
an optional reason to explain the response code - e.g. |
|
the time the request was received in milliseconds |
|
the port used for the request |
|
the scheme (HTTP/HTTPS) used for the request |
|
an optoinal message associated with a proxy error |
|
the type of elasticsearch request (e.g. search/bulk etc) |
|
the cluster the request was forwarded to |
|
a unique ID for each request (returned on the response as |
|
a code indicating the TLS version used for the request - |
|
the number of instances in the target cluster |
|
the type of cluster the request was routed to (e.g. elasticsearch, kibana, apm etc) |
|
the HTTP method for the request |
|
the amount of time taken for the upstream request, the proxy latency is |
|
a unique ID for the upstream request to the product, the proxy maintains connection pools so this should be re-used |