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
We need a simple and modern way to manage our logs so that when an issue
occurs, we can debug it easily. We now have a way to do this via
Fluent Bit Loki Plugin. Reasons for going with fluent-bit:
a light machine and not have to worry about it, we can also share the
host for main backend and fluent-bit.
redirect our logs to a different log management service, receive logs
in various ways, filter log messages, etc.
This lets us output our logs to Granfa Loki, Logzio, Datadog, StdOut, etc all
at the same time.
Notes from this PR:
I've included an example config file for fluent-bit at
telemetry/fluent-bit/fluent-bit.toml.example
which we can use for deploying a sort of sidecar for logs.HTTP
to our local-to-server fluent-bit instance and FluentBit forwards those those logs to Grafana Loki (we can actually change the output to other providers too)Signed-off-by: jay-dee7 [email protected]