Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow passing more arguments to the log forwarder #43

Open
plumdog opened this issue Apr 7, 2022 · 1 comment
Open

Allow passing more arguments to the log forwarder #43

plumdog opened this issue Apr 7, 2022 · 1 comment

Comments

@plumdog
Copy link

plumdog commented Apr 7, 2022

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 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.
@sunshineo
Copy link

+1, we need to change the memory size of the lambda

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants