Apigee Logs not showing large responses or no response being logged at all

Hello.
I'm experiencing an issue with Apigee logs. Responses exceeding 502KB, which are currently handled as pass-through for a specific endpoint, are not being captured in the logs. Are there any alternative approaches or workarounds to capture these larger responses?

@dchiesa1 @kurtkanaskie

 

Solved Solved
2 3 112
1 ACCEPTED SOLUTION

Work around options on these are

1. Make sure log data is <256 KB. 

2. Move your entire logging to some where else, say elastic search or storage bucket. Both of them provide api or the pub-sub of GCP could be used and the external loggers could be a subscriber to these topics

 

View solution in original post

3 REPLIES 3

I presume you are logging to Cloud Logging, in which case there is a log entry limit of 256 KB as documented here: https://cloud.google.com/logging/quotas#log-limits

Thanks @kurtkanaskie, we understand the Cloud Logging limitation and are interested in exploring workarounds to capture responses in Apigee logs. Is there any solution to capture responses despite the known Cloud Logging limitation?

Work around options on these are

1. Make sure log data is <256 KB. 

2. Move your entire logging to some where else, say elastic search or storage bucket. Both of them provide api or the pub-sub of GCP could be used and the external loggers could be a subscriber to these topics