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

[aws-for-fluent-bit] cloudWatchLog Opt In #998

Open
TheWorldWideWebb opened this issue Sep 8, 2023 · 0 comments · May be fixed by #1168
Open

[aws-for-fluent-bit] cloudWatchLog Opt In #998

TheWorldWideWebb opened this issue Sep 8, 2023 · 0 comments · May be fixed by #1168
Labels
enhancement New feature or request

Comments

@TheWorldWideWebb
Copy link

Hi,

Noticed when upgrading from 0.1.21 to 0.1.28 that during 0.1.24 cloudWatch was disabled by default and cloudWatchLogs was enabled.

The projects versioning looks like a typical SemVar approach so I wasn't expecting any issues with this bump but encountered the default config for cloudWatchLogs and an excess of failed transformation mapping logs. Just wanted to highlight that an opt in approach for cloudWatchLogs (and future C implementations) might have a smoother upgrade path, or just a bump to 0.2.X.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
1 participant