Optional output field?

[pirxthepilot]

Motivation

In an effort to make events coming from Falco as compact as possible, I would like to set json_include_output_property to false. However, it looks like falcosidekick does not accept events that do not have the output field (here and here).

Feature

Would it be possible for falcosidekick to accept events that do not have the output field? Thanks!

[Issif]

You're right, these fields are mandatory, what's your use case exactly? Even with them, the size of the payload is quite small and these fields are really useful for a lot of systems (eg response engine)

[pirxthepilot]

Hi Thomas, our falco config is generating a lot of events (on purpose) and so every bit of savings in the message size helps. The messages ultimately end up in a SIEM where only output_fields is used, aside from the rule name, priority and timestamp, so we really do not need output. We also have a few rules where we collect a lot of fields so the output can get quite big. And if falco itself supports not having the output field, I'm hoping sidekick can support it too.

Thanks!

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[Issif]

/remove-lifecycle stale

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[poiana]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh with /remove-lifecycle rotten.

Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle rotten

[poiana]

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/close

[poiana]

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[Issif]

reopen
/remove-lifecycle rotten