We have a message logging policy in place for the post-client flow. This logging mechanism is functioning properly for most APIs but not for one particular API, as its requests are failing with a 500 error. Additionally, the log size for these requests is exceeding 1MB, preventing the message logging system from sending logs to QRadar. Could you please assist me in configuring all logs to adhere to a maximum size of 1MB?
Below message logging configuration provided
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<MessageLogging continueOnError="false" enabled="true" name="ML-LogToSysLogServer">
<DisplayName>ML-LogToSysLogServer</DisplayName>
<Syslog>
<Message defaultVariableValue="unknown">
time={system.time.year}-{system.time.month}-{system.time.day} {system.time.hour}:{system.time.minute}:{system.time.second} message_id={messageid} environment_name={environment.name} request_verb={request.verb} response_status_code={response.status.code} error_status_code={error.status.code} error_message={error.message} error_reason={error.reason.phrase} fault_name={fault.name} fault_reason={fault.reason}
client_host={proxy.client.ip} apiproxy_name={apiproxy.name} apiproduct_name={verifyapikey.VerifyAPIKey.apiproduct.name} app_name={verifyapikey.VerifyAPIKey.developer.app.name} proxy_basepath={proxy.basepath} proxy_pathsuffix = {proxy.pathsuffix} target_url = {target.url}
</Message>
<Host>#########</Host>
<Port>###</Port>
<Protocol>UDP</Protocol>
<FormatMessage>true</FormatMessage>
<DateFormat>yyMMdd-HH:mm:ss.SSS</DateFormat>
</Syslog>
</MessageLogging>
@dchiesa1 @apigee
LinkedIn
Twitter
