-
Notifications
You must be signed in to change notification settings - Fork 30
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
Is this now deprecated in favour of the vanilla Firehose plugin? #75
Comments
I think the same answer will probably apply for the firehose plugins. Though getting feature parity in the core plugin would be easier for Firehose than for Cloudwatch. |
Action Item: Clarify this in a note in this repo's readme and in the core Fluent Bit documentation. I think we should also print a statement when this plugin's code starts up reminding people to check out the new one and migrate if they can. We will keep this one around, but we do want people to migrate to the new/better plugin. |
A notice has been added in README: #82. This issue will be closed. |
For future reference, linking this comment by PettitWesley:
|
Thanks. I'm also actively working on this feature request, but implementing it in the core plugin. The plugin in this repo will soon have a feature gap. |
I see that v1.6 of upstream/vanilla Fluent Bit now includes its own output plugin for writing to Firehose, and says this:
However, I don't see any corresponding deprecation notice here. So, to clarify:
a) The Amazon-flavour Fluent Bit Docker image (containing this Amazon-flavour Firehose plugin)
OR
b) The vanilla Fluent Bit Docker image (containing the new vanilla Firehose plugin)
The text was updated successfully, but these errors were encountered: