-
Notifications
You must be signed in to change notification settings - Fork 183
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
Send output_fields
to Loki
#1090
Comments
Hi, The However, it's already possible to list the
For example: loki:
extralabels: "container.name, container.id" Does it fit with your needs? |
Thank you for the quick answer, |
Ok I see now what you meant. It's pretty easy add a new config option: loki:
format: text # format for the log entry: text, json (default: text) |
By checking for your PR, I noticed some improvements to do for the Loki output, I included your request in the same PR: #1091 |
That was fast, thank you very much! <3 |
I can't give you any ETA for the release. If it's urgent, you can still use the master branch like this (with an Helm deployment): falcosidekick:
image:
tag: master
config:
extraEnv:
- LOKI_FORMAT: json |
Motivation
Currently, when using Loki to store events from falco sidekick, only the
output
string is sent (source code). It cause issue to properly parse the event, and is missing informations. Other destinations seems to support sendingoutput_fields
.Feature
Add the ability to send output_fields instead of output to Loki, either by default or with an aditionnal configuration like
send_json_output
or something.Alternatives
Improve the formatting of the logfmt
output
string, by quoting values containing a space.Additional context
I would be happy to provide a pull request, I just need some guidance on how to integrate the change (retro-compatibility, configuration, defaults...)
The text was updated successfully, but these errors were encountered: