Skip to content

Conversation

@rabbitstack
Copy link
Owner

What is the purpose of this PR / why it is needed?

This PR introduces a change to avoid compiling the ruleset if Fibratus is instructed to run the filament.

What type of change does this PR introduce?


Uncomment one or more /kind <> lines:

/kind feature (non-breaking change which adds functionality)

/kind bug-fix (non-breaking change which fixes an issue)

/kind refactor (non-breaking change that restructures the code, while not changing the original functionality)

/kind breaking (fix or feature that would cause existing functionality to not work as expected

/kind cleanup

/kind improvement

/kind design

/kind documentation

/kind other (change that doesn't pertain to any of the above categories)

Any specific area of the project related to this PR?


Uncomment one or more /area <> lines:

/area instrumentation

/area telemetry

/area rule-engine

/area filters

/area yara

/area event

/area captures

/area alertsenders

/area outputs

/area rules

/area filaments

/area config

/area cli

/area tests

/area ci

/area build

/area docs

/area deps

/area other

Special notes for the reviewer


Does this PR introduce a user-facing change?


Avoid compiling ruleset if the Fibratus is
instructed to the run the filament.
@rabbitstack rabbitstack linked an issue Jun 30, 2025 that may be closed by this pull request
@rabbitstack rabbitstack merged commit 1dd69e3 into master Aug 5, 2025
14 of 15 checks passed
@rabbitstack rabbitstack deleted the disable-rule-engine-if-filament-set branch August 5, 2025 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Some events can't be collected with filaments

2 participants