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 want to be able to pass parameters to the forwarder stack, eg ExcludeAtMatch to filter out some less useful logs, namely the START/END/REPORT chatter from Lambda.
Actual Behavior
Cannot configure the Log Forwarder other than the function name, Datadog site and API key to use.
Possible solutions
Add lots of parameters to the template in this repo to allow full customisation of the Forwarder stack.
Add an option to not deploy the forwarder in this template, but support deploying it separately.
Is there a different way of filtering the logs that are shipped from Lambda to Datadog? In my case, these are the "platform" logs from Lambda, not from my application code.
The text was updated successfully, but these errors were encountered:
Expected Behavior
The template at https://github.com/DataDog/cloudformation-template/blob/master/aws/main.yaml has a resource
ForwarderStack
that wraps the forwarder which I believe comes from https://github.com/DataDog/datadog-serverless-functions/blob/master/aws/logs_monitoring/template.yaml.I want to be able to pass parameters to the forwarder stack, eg
ExcludeAtMatch
to filter out some less useful logs, namely theSTART
/END
/REPORT
chatter from Lambda.Actual Behavior
Cannot configure the Log Forwarder other than the function name, Datadog site and API key to use.
Possible solutions
The text was updated successfully, but these errors were encountered: