APIGEE log truncation on Elastic logstash end

csd · 07-11-2023 10:05 PM

We have a message logging policy as a part of PostClientFlow which looks as follows

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<MessageLogging async="false" continueOnError="false" enabled="true" name="ml-log2-logstash">
    <DisplayName>ml-log2-logstash</DisplayName>
    <Syslog>
        <Message>{logging-message}</Message>
        <Host>.....</Host>
        <Port>....</Port>
        <Protocol>TCP</Protocol>
        <PayloadOnly>true</PayloadOnly>
    </Syslog>
</MessageLogging>

The logging-message variable is JSON stringified payload and we send the log to Logstash to be later queried.

We are seeing that payload sent from APIGEE fails to parse at the Logstash end. We checked at our end and do not see any sort of limitations on incoming payload.

Hence not sure what is causing the log truncation.

This is severely affecting our ability to trace the user journey due to missing logs in our index.

Any help would be appreciated.