Parameter | Description |
Store Request | Logs all requests. |
Store Response | Logs all responses. |
Compress Payload Data | Compresses the logged payload data. |
Log Generation Frequency | Specifies how frequently to log the payload. Select one of the following options: Always. Logs all requests and responses. On Failure. Logs only the failed requests and responses. On Success. Logs only the successful responses and requests. |
Destination | Specifies the destination where to log the payload. Select the required options: API Gateway API Portal Audit Log CentraSite Note: This option is applicable only for the APIs published from CentraSite to API Gateway. Digital Events Elasticsearch Email (you can add multiple email addresses by clicking ). Note: If an email alias is available, you can type the email alias in the Email Address field with the following syntax, ${emailaliasname}. For example, if test is the email alias, then type ${test}. JDBC Local Log: You can select the severity of the messages to be logged (logging level) from the Log Level drop-down list. The available log levels are ERROR, INFO, and WARN. Set the Integration Server Administrator's logging level for API Gateway to match the logging levels specified for the run-time actions (go to Settings > Logging > Server Logger). For example, if a Log Invocation action is set to the logging level of Error, you must also set Integration Server Administrator's logging level for API Gateway to Error. If the action's logging level is set to a low level (Warning-level or Information level), but Integration Server Administrator's logging level for API Gateway is set to a higher level (Error-level), then only the higher-level messages are written to the log file. Entries posted to the local log are identified by a product code of YAI and suffixed with the initial alphabet of the logging level selected. For example, for an error level, the entry appears as [YAI.0900.0002E]. SNMP |