-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Comments
+1. This would be huge for orgs running in AWS! |
+1 yes please |
+1 pretty pls. |
+1! |
+1 |
1 similar comment
+1 |
Is there any chance, for this being implemented soon? |
This would be a big benefit for lot of AWS customers |
@edsiper @leonardo-albertovich @nokute78 any chance fluentbit could provide CloudWatch Infrequent Access (%50 cost saving in log ingest) in the roadmap? |
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 |
This issue was closed because it has been stalled for 5 days with no activity. |
Can this be reopened seems like there is a lot of interest. |
See #8832 |
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.
The text was updated successfully, but these errors were encountered: