We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Evaluate fluent-operator to deploy collector/aggregator log architecture based on fluent-bit and fluentd
Fluent Operator includes CRDs and controllers for both Fluent Bit and Fluentd which allows to control logs data pipelines in 3 modes:
Moreover, Fluentd helm chart does not seem to be maintained anymore.
The text was updated successfully, but these errors were encountered:
Operator uses ad-hoc docker images kubesphere/fluentd and kubesphere/fluent-bit that comes preconfigured with a set of supported plugins
kubesphere/fluentd
kubesphere/fluent-bit
Currently I am using for Fluentd aggregator layer a customized fluentd image containing following plugins:
All of them supported by Operator's fluentd image except fluent-plugin-prometheus
fluent-plugin-prometheus
There is an open issue asking to include support for that plugin: fluent/fluent-operator#725
This missing capability is a stopper. Current implementation cannot be migrated to Fluent Operator
Currently I am using the following fluent-bit plugins
All of them supported currently by the Operator's image
Prometheus integration is also supported: https://github.com/fluent/fluent-operator/blob/master/docs/best-practice/monitoring.md
Sorry, something went wrong.
No branches or pull requests
Scope
Evaluate fluent-operator to deploy collector/aggregator log architecture based on fluent-bit and fluentd
Fluent Operator includes CRDs and controllers for both Fluent Bit and Fluentd which allows to control logs data pipelines in 3 modes:
Moreover, Fluentd helm chart does not seem to be maintained anymore.
References
The text was updated successfully, but these errors were encountered: