You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I spent a while today debugging an alert for a large percentage of 5XX responses from a cdk-configured GuApiLambda. It turned out the lambda is taking longer than 30 seconds on each invocation, and so the API Gateway is timing out. However, this was a little hard to debug, because the API Gateway logs (as distinct from the lambda logs) were disabled – I was able to turn them on in the web UI, but had to be shown that that was possible.
Would it be possible for those logs to be enabled by default if using the GuApiLambda (and ideally sent to the same log group as the lambda’s logs)? I think it would be helpful for people debugging errors like these in the future.
The text was updated successfully, but these errors were encountered:
I spent a while today debugging an alert for a large percentage of 5XX responses from a cdk-configured GuApiLambda. It turned out the lambda is taking longer than 30 seconds on each invocation, and so the API Gateway is timing out. However, this was a little hard to debug, because the API Gateway logs (as distinct from the lambda logs) were disabled – I was able to turn them on in the web UI, but had to be shown that that was possible.
Would it be possible for those logs to be enabled by default if using the GuApiLambda (and ideally sent to the same log group as the lambda’s logs)? I think it would be helpful for people debugging errors like these in the future.
The text was updated successfully, but these errors were encountered: