Skip to content
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

Adding a custom logger as an event input source #526

Open
wzyhay opened this issue Sep 9, 2024 · 1 comment
Open

Adding a custom logger as an event input source #526

wzyhay opened this issue Sep 9, 2024 · 1 comment
Labels
kind/feature New feature or request lifecycle/stale

Comments

@wzyhay
Copy link

wzyhay commented Sep 9, 2024

Motivation
When I add rules for custom data sources, it is not always so convenient. Can the team add new event sources for rule debugging, such as logs or test demos?

Feature
The scenario is that there is a huge event stream, which requires a lot of rules to filter alarms, but it is also necessary to verify whether each rule is effective. The event source of the existing plug-in is not so convenient to use. It would be great if users could write a log file to simulate adding corresponding logs and use it as an input source to verify whether the custom rules can be hit normally through the engine.

Alternatives

Additional context

@wzyhay wzyhay added the kind/feature New feature or request label Sep 9, 2024
@poiana
Copy link
Contributor

poiana commented Dec 8, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request lifecycle/stale
Projects
None yet
Development

No branches or pull requests

2 participants