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

How do I use retention_in_days configurations #245

Open
mukundjalan opened this issue May 18, 2022 · 1 comment
Open

How do I use retention_in_days configurations #245

mukundjalan opened this issue May 18, 2022 · 1 comment

Comments

@mukundjalan
Copy link

Problem

We have used these configurations to create the cloudwatch groups. Now we wish to update the retention period in all the places using the retention_in_days config. I updated the config map in kubernetes, but it had no impact. I am unable to understand if retention_in_days works only on create or am I using it wrongly for update.

While searching, I came across retention_in_days_key. From the description use specified field of records as retention period, I am unable to make any use of it. Also, there seems to be no example or additional documentation related to the same.

Expected Behavior or What you need to ask

I would like to know how can I update the cloudwatch log retention period by updating the fluentd configuration config map

@hfinucane
Copy link

Check your logs for something like

failed to flush the buffer. retry_times=0 next_retry_time=2022-08-04 21:36:46 +0000 chunk="5e5712512d03a1ab530441bceee19785" error_class=Aws::CloudWatchLogs::Errors::AccessDeniedException error="User:blahblahblah is not authorized to perform: logs:PutRetentionPolicy on resource: arn:aws:logs:yadayadayada: because no identity-based policy allows the logs:PutRetentionPolicy action"

Fluentd is going to need the logs:PutRetentionPolicy permission bit set to write that.

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