Skip to content

Conversation

@rabbitstack
Copy link
Owner

@rabbitstack rabbitstack commented Aug 6, 2025

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

The rule engine compiler ensures that the provided event or category names match the internal catalog nomenclature.

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?


@rabbitstack rabbitstack force-pushed the validate-event-and-category-field-values branch from b78cb7b to 66c1bd4 Compare August 7, 2025 16:28
The rule engine compiler ensures that the provided
event or category names are match the internal catalog
nomenclature.
@rabbitstack rabbitstack merged commit 18c7d00 into master Aug 8, 2025
11 checks passed
@rabbitstack rabbitstack deleted the validate-event-and-category-field-values branch August 8, 2025 21:45
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.

2 participants