-
Notifications
You must be signed in to change notification settings - Fork 182
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
Log pushes for Kubernetes Audit Events to Loki are failing #181
Comments
@Issif just as verification, its working now with the latest image |
@fjogeleit I have the same problem. how did you solve it. |
I see it either, 50% events to loki. Very simple log on sidekick side. Could
mind
and
I do have some local modifications (but aware of these .. ) going to try to skip value with missing key.. now |
possibly related https://githubhelp.com/falcosecurity/falcosidekick/issues/77 |
The Loki output for next release 2.27 will be upgraded, hope it will help you #356 |
The 2.27.0 is out, and the helm charts are updated falco.org/blog/falcosidekick-2-27-0-ui-2-1-0 |
@Issif I get this issue in falcosidekick 2.27v version as well ? Do we have any fix for it?
|
First time I see this issue. Are you sure your hosts' times are correct? I see a big diff between the log line of falcosidekick (2023/06/12 09:00:48) and the timestamp of the event 2023-06-11 20:50:23.331614 +0000 UTC). |
Describe the bug
I'm using falcosidekick to send host os events and Kubernetes audit events to Grafana Loki. If a host os rule is triggered, the event is send to Loki as expected. If I trigger a Kubernetes Audit Event the push to Loki failed with 400 - Header Missing.
Working example for Host Rule:
The Example described in the Documentation https://falco.org/docs/event-sources/kubernetes-audit/#example failed:
How to reproduce it
Expected behaviour
Sends Kubernetes Audit Events successfully to Loki
Screenshots
See the issue description
Environment
Falco 0.27.0
Driver version: 5c0b863ddade7a45568c0ac97d037422c9efb750
{
"machine": "x86_64",
"nodename": "dev-node-3",
"release": "5.11.0-051100rc6-generic",
"sysname": "Linux",
"version": "#202101312230 SMP Sun Jan 31 22:33:58 UTC 2021"
}
The text was updated successfully, but these errors were encountered: