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
Feature proposal for more granular AWS API Gateway logging
Description
Actual behavior:
Enabling logging at the API GW level via provider->logs->restApi=true is useful, but it also adds "log full requests/responses data" (/*/*/logging/dataTrace), which may not be desired due to compliance requirements or just plain cost concerns
Cloudwatch basic logs, cloudwatch full (dataTrace) logs, and access logging can be individually enabled/disabled.
Nice to have: have option of overriding the access log format and CloudWatch Group (in a shared API GW situation, you don't want the service name being encoded into the CloudWatch Group).
The text was updated successfully, but these errors were encountered:
This would be nice but I wonder why SLS is even touching those settings when they're not specified. SLS allows for externally created API gateway to be used but whenever a deployment happens it resets the logging settings. It should not touch them unless logs block is specified in SLS config.
Feature proposal for more granular AWS API Gateway logging
Description
Actual behavior:
/*/*/logging/dataTrace
), which may not be desired due to compliance requirements or just plain cost concernsserverless/lib/plugins/aws/package/compile/events/apiGateway/lib/hack/updateStage.js
Line 193 in 0b53d71
Desired behavior:
Nice to have: have option of overriding the access log format and CloudWatch Group (in a shared API GW situation, you don't want the service name being encoded into the CloudWatch Group).
The text was updated successfully, but these errors were encountered: