AWS CloudWatch Logs - create infrequent access type with `create_missing_group` · vectordotdev/vector#22008

(3 评论) (3 反应) (0 负责人)Rust (21,837 star) (2,126 fork)batch import

good first issuesink: aws_cloudwatch_logs

描述

A note for the community

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Use Cases

When creating AWS CloudWatch log groups, there are two types: standard and infrequent access (see: https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatch_Logs_Log_Classes.html).

By default, the create_missing_group will select the standard type. There are no options to select which type of log group to create.

Attempted Solutions

Workaround

We can create the log group manually through the AWS CLI or interface and then disable create_missing_group. We point vector to the pre-created log group and it would work.

This works if you have a low number of log groups, but if you have hundreds or if the log groups are dynamically generated, this is not feasible.

Proposal

Have an option to select the type of log group via the create_missing_group

References

No response

Version

0.42.0

贡献者指南

技术栈: rustaws
领域: cloudobservability
议题类型: feature
难度: 3
预计时间: half day
活动状态: active
清晰度: clear
前置要求: Rust programmingAWS CloudWatch LogsVector sink architecture
新手友好度: 60
研究方向: Examine the AWS CloudWatch Logs sink configuration in `src/sinks/aws cloudwatch logs/` to understand how `create missing group` is implemented. Review the AWS SDK for Rust's `CreateLogGroupInput` to see how the `logGroupClass` field is set. Propose a new configuration option to choose between 'STANDARD' and 'INFREQUENT ACCESS' log group types, and implement the change in the sink's code. Ensure tests are updated to cover the new option.