Request-log (Section)#

Path: /environments/environment/logging/request-log

The fields included in the request log. A field is included when its configured Level is the same, or finer, than the RequestReceiver Logger Level.

Parameters#

NameTypeRequiredDefaultDescription
clientenumeration (info, debug, off)optionaldebugThe IP address of the caller (potentially that of a reverse proxy)
locationenumeration (info, debug, off)optionaldebugThe geolocation of the client, when a geolocation provider is available
paramsenumeration (info, debug, off)optionaldebugThe HTTP query string and form parameters, or the JSON request body. Any other body is logged as a placeholder, unless log-unparsed-request-body is enabled. This may contain sensitive data, use masked-parameter-pattern to hide the values of such parameters
masked-parameter-patternstring (length: 1..9223372036854775807)optional-A Java regular expression selecting the request parameters whose values are replaced by a fixed mask in the params field. The expression matches each parameter name anywhere unless it is anchored: for example, ‘password’ hides both ‘password’ and ‘new_password’. Use ’(?i)’ to ignore case, or ’^’ and ’$’ to match the whole name. Parameters can come from the query string, a form body or a JSON body, where the names of nested objects are matched as well. When not configured, no parameter is masked.
log-unparsed-request-bodybooleanoptionalfalseWARNING: this is potentially dangerous, and should only be enabled temporarily, to debug a problem. When enabled, a request body that cannot be read as parameters is logged as it is in the params field: a body declared as JSON that is not valid JSON, or a body whose content type is neither JSON nor an HTML form. Such a body may contain passwords, tokens and personal data, which are written to the request log without any masking. For that reason, this cannot be enabled together with masked-parameter-pattern. When disabled, such a body is not logged: params is logged as ‘<INVALID JSON>’, ‘<UNLOGGABLE JSON>’ or ‘<UNSUPPORTED CONTENT TYPE>’ instead.
protocolenumeration (info, debug, off)optionalinfoThe HTTP protocol used
langenumeration (info, debug, off)optionalinfoThe value of the Accept-Language request header
acceptenumeration (info, debug, off)optionalinfoThe value of the Accept request header
request-headersenumeration (info, debug, off)optionaldebugAll HTTP request headers. This may contain sensitive data
response-headersenumeration (info, debug, off)optionaldebugAll HTTP response headers. This may contain sensitive data
sizeenumeration (info, debug, off)optionalinfoThe size of the HTTP response body
content-typeenumeration (info, debug, off)optionalinfoThe content type of the HTTP response body
secureenumeration (info, debug, off)optionalinfoWhether the connection was made over HTTPS, and if so, whether a client certificate was used
durationenumeration (info, debug, off)optionalinfoHow long the request took to process, in milliseconds

Was this helpful?