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

Support Backup Outputs #1632

Open
PettitWesley opened this issue Oct 9, 2019 · 3 comments
Open

Support Backup Outputs #1632

PettitWesley opened this issue Oct 9, 2019 · 3 comments
Labels
long-term Long term issues (exempted by stale bots)

Comments

@PettitWesley
Copy link
Contributor

PettitWesley commented Oct 9, 2019

Is your feature request related to a problem? Please describe.

Problem: Something goes wrong and Fluent Bit is unable to send to your log destination. May be the destination goes down, or some network or other config prevents Fluent Bit from reaching it.

Proposed Solution: Specify a second output plugin as backup for another output. You'd be able to configure a timeout/threshold for when Fluent Bit switches to the backup output. (May be number of failed retries, number of errors, or something like the time since the first unsuccessful send).

Compared to other existing feature requests and open issues, I do not think this is very high priority. I'm interested in seeing if anyone else thinks this would be useful. Plus one if you agree and comment if you want to discuss how this would work!

@github-actions github-actions bot added the Stale label Feb 3, 2022
@PettitWesley PettitWesley added long-term Long term issues (exempted by stale bots) and removed Stale labels Feb 7, 2022
@fluent fluent deleted a comment from github-actions bot Feb 7, 2022
@matthewfala
Copy link
Contributor

I feel like this is an important feature. A primary goal of Fluent Bit should be: Never loose data, and having backup output plugins would help achieve this goal.

@artheus
Copy link

artheus commented Mar 28, 2023

I strongly agree. As many of the companies that uses fluent-bit will want to get all their data. This is important for statistics, analysis, anomaly detection, security monitoring and so on. So loosing a tiny bit of data, might sound insignificant, but can actually have major consequences.

@Shrey29ansh
Copy link

Any updates?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
long-term Long term issues (exempted by stale bots)
Projects
None yet
Development

No branches or pull requests

4 participants