APIRef_tm_ltm_profile_request-log¶
mgmt/tm/ltm/profile/request-log
Virtual server request logging profile configuration
REST Endpoints
- Collection URI
/mgmt/tm/ltm/profile/request-log- Collection Methods
OPTIONS, GET- Resource URI
/mgmt/tm/ltm/profile/request-log/~resource id- Resource Methods
OPTIONS, GET, PUT, PATCH, DELETE, POST- Resource Natural Key
name, partition, subPath
Properties
| Name | Type | Default Value | Required | Access | Description |
|---|---|---|---|---|---|
appService |
string | optional | read/write | The application service to which the object belongs. | |
defaultsFrom |
string | optional | read/write | Specifies the profile that you want to use as the parent profile. Your new profile inherits all settings and values from the parent profile specified. | |
description |
string | optional | read/write | User defined description. | |
logRequestLoggingErrors |
string | no | optional | read/write | Enables secondary logging should the primary lack sufficient available bandwidth. This mechanism is best used to send an alert to a completely separate destination. |
logResponseByDefault |
string | yes | optional | read/write | Response logging may be overridden via iRule. This field determines the default response action. |
logResponseLoggingErrors |
string | disabled | optional | read/write | Enables secondary logging should the primary lack sufficient available bandwidth. This mechanism is best used to send an alert to a completely separate destination. |
tmPartition |
string | Common | optional | read/write | Displays the administrative partition within which this profile resides. |
proxyCloseOnError |
string | no | optional | read/write | If enabled, the logging profile will close the connection after sending its proxy-response. |
proxyRespondOnLoggingError |
string | no | optional | read/write | Should the logging fail, this feature allows the logging profile to respond directly, eg with an HTTP 502. |
proxyResponse |
string | optional | read/write | The response to send on logging errors. | |
requestLogErrorPool |
string | optional | read/write | Name of the pool from which to select log servers. | |
requestLogErrorProtocol |
string | mds-udp | optional | read/write | HighSpeedLogging protocol to use when logging. |
requestLogErrorTemplate |
string | optional | read/write | The template to use when generating log messages. Shell style escapes (eg $foo and/or ${foo}) are used to import transaction-specific values. | |
requestLogPool |
string | optional | read/write | Name of the pool from which to select log servers. | |
requestLogProtocol |
string | mds-udp | optional | read/write | HighSpeedLogging protocol to use when logging. |
requestLogTemplate |
string | optional | read/write | The template to use when generating log messages. Shell style escapes (eg $foo and/or ${foo}) are used to import transaction-specific values. | |
requestLogging |
string | enabled | optional | read/write | Enables or disables logging before the request is proxied. |
responseLogErrorPool |
string | optional | read/write | Name of the pool from which to select log servers. | |
responseLogErrorProtocol |
string | mds-udp | optional | read/write | HighSpeedLogging protocol to use when logging. |
responseLogErrorTemplate |
string | optional | read/write | The template to use when generating log messages. Shell style escapes (eg $foo and/or ${foo}) are used to import transaction-specific values. | |
responseLogPool |
string | optional | read/write | Name of the pool from which to select log servers. | |
responseLogProtocol |
string | mds-udp | optional | read/write | HighSpeedLogging protocol to use when logging. |
responseLogTemplate |
string | optional | read/write | The template to use when generating log messages. Shell style escapes (eg $foo and/or ${foo}) are used to import transaction-specific values. | |
responseLogging |
string | enabled | optional | read/write | Enables or disables logging before the response is returned to the client. |
Copyright (c) 2016, F5 Networks Inc. All Rights Reserved.
The BIG-IP API Reference documentation contains community-contributed content. F5 does not monitor or control community code contributions. We make no guarantees or warranties regarding the available code, and it may contain errors, defects, bugs, inaccuracies, or security vulnerabilities. Your access to and use of any code available in the BIG-IP API reference guides is solely at your own risk.