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

CloudWatch log classes support #8220

Closed
SamuraiPrinciple opened this issue Nov 27, 2023 · 13 comments
Closed

CloudWatch log classes support #8220

SamuraiPrinciple opened this issue Nov 27, 2023 · 13 comments
Labels

Comments

@SamuraiPrinciple
Copy link

Is your feature request related to a problem? Please describe.
With the newly announced support for CloudWatch log classes:

https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatch_Logs_Log_Classes.html

it would be very nice if cloudwatch_logs output were to support creating log groups with Infrequent Access log class.

Describe the solution you'd like
Any reasonably ergonomic way of configuring fluentbit cloudwatch_logs output so that created log groups have Infrequent Access log class.

Describe alternatives you've considered
Alternative is for all the log groups to be pre-created with correct log class.

Additional context

Infrequent Access log class makes it possible to achieve operational savings.

@cristianmagana
Copy link

+1. This would be huge for orgs running in AWS!

@azastawski
Copy link

+1 yes please

@serkanh
Copy link

serkanh commented Dec 6, 2023

+1 pretty pls.

@dagnai
Copy link

dagnai commented Jan 30, 2024

+1!

@snehagg24
Copy link

+1

1 similar comment
@pieterjanverbruggen
Copy link

+1

@adanecki
Copy link

Is there any chance, for this being implemented soon?

@mutchida
Copy link

This would be a big benefit for lot of AWS customers

@cristianmagana
Copy link

@edsiper @leonardo-albertovich @nokute78 any chance fluentbit could provide CloudWatch Infrequent Access (%50 cost saving in log ingest) in the roadmap?

Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.

@github-actions github-actions bot added the Stale label Jul 11, 2024
Copy link
Contributor

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 16, 2024
@boarder7395
Copy link

Can this be reopened seems like there is a lot of interest.

@SamuraiPrinciple
Copy link
Author

SamuraiPrinciple commented Aug 19, 2024

Can this be reopened seems like there is a lot of interest.

See #8832

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

No branches or pull requests

10 participants