opensearch-project / opensearch-project/security-analytics
[FEATURE] Custom Rules - auto field mapping control
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 111
- Forks
- 111
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 13
Description
Is your feature request related to a problem?
Currently when user is ingesting custom rules, we're automatically rewriting rule field names based on mappings in fieldmappings.yml file. User is unaware if any of fields are actually rewritten, and if they are, there is no information to what exact field are they rewritten.
Example:
Let's say user has field called RunningProcessName in log index and user ingested and enabled custom rule which uses this field in selection query. If RunningProcessName is present in fieldmappings.yml for this particular rule category, Rule would be rewritten to mapped value without user knowledge and Rule won't be working.
What solution would you like?
When ingesting custom rules, make automatic field rewrite disabled by default. Possibly make this as a setting/checkbox on Rule create flow.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing custom-rule ingestion and the Rule create flow, then inspect how fieldmappings.yml is applied during rule processing. Done means automatic field rewriting is disabled by default and the create flow provides the requested explicit control, with the resulting behavior verified for custom rules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100