-
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
Feature Request: MQTT Output #674
Comments
@MichaelBerryman is this issue still relevant to your interests? It sounds quite doable at a first take. |
Is there any update on this? |
Is this enhancement planned in the near future? |
Is there an update on this feature? It would be also quite useful for us. |
any update on this feature ? |
MQTT Output can be very interesting for example to use FluentBit coupled with projects like eKuiper, https://ekuiper.org, in the Edge, to add additional stream processing functions to the ones that FluentBit already provides. Maybe if already exists MQTT Input in FluentBit, create MQTT Output is not much effor for the developers of FluentBit, and it can be a great additional feature. |
Add MQTT Output to FluentBit can supercharge Stream Processing options in FluentBit, thanks to eKuiper |
Do we have any updates on this? |
Still thinking that MQTT Output can be a really good differential for FluentBit compared to other event collectors... |
We'd like to collect logs via the systemd input plugin and output to mqtt.
We're running balena (docker lite) on an arm64 sensor fleet and would like to get the docker logs back to a central store. We've chosen to use mqtt as it's light weight. We have to collect the logs from systemd / journald as balena doesn't support the fluentd logging driver :(
The text was updated successfully, but these errors were encountered: