adding openobserve for 3.1 #1473
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Chaitanya Sistla <[email protected]>
chaitanya-sistla
force-pushed
the
feature/o2-3.1
branch
from
999c800 to
a1ed83b
Compare
Contributor
Author
|
@patrick-stephens let me know if this looks good. Also as mentioned, I do not see OpenObserve details at https://docs.fluentbit.io/manual/3.2-dev/pipeline/outputs/openobserve |
Contributor
|
I'll have to dive into gitbook, sometimes it gets "stuck" |
patrick-stephens
approved these changes
Oct 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
This PR adds OpenObserve (O2) as a supported output destination for Fluent Bit, allowing users to forward logs seamlessly to O2. The integration works without any code or implementation changes, as Fluent Bit's existing configuration system can handle the output forwarding.
Context:
There isn't an open issue for this feature, but adding OpenObserve as an output destination can provide users with an efficient logging solution. Since no code modifications are necessary, this update can be applied without concerns.