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

Disable cloud watch logs conditionally for Telemetry API #2

Open
bajajyog opened this issue Apr 13, 2023 · 1 comment
Open

Disable cloud watch logs conditionally for Telemetry API #2

bajajyog opened this issue Apr 13, 2023 · 1 comment

Comments

@bajajyog
Copy link

Logs are still going to AWS cloud watch even after subscribing to AWS Lamabda Telemetry API.

I want extensions logs to still go to AWS cloud watch but not AWS Lambda function application logs.

Please advise, how to conditional disable cloud watch logs from AWS Lambda

@saartochner-lumigo
Copy link
Contributor

Hi,
Indeed, when subscribing to the AWS Lambda Telemetry API, the logs continue to be written to AWS CloudWatch.
If you wish to prevent the lambda from writing logs to CloudWatch, the most straightforward approach is to remove its permissions. You can find more details here: https://stackoverflow.com/questions/51166504/disable-cloudwatch-to-monitor-logs-for-lambda-function

Currently, there is no direct way to block only a subset of logs from being written to CloudWatch. However, a more robust solution could be achieved using our extension:
Just add CloudWatch as a new sink along with a filter on the logs. It should be easy and straightforward, and it will give you the desired behavior.

I hope this clarifies your options. If you have any further questions, feel free to ask.
Thanks!

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