Thanks for sharing the idea. I want to make sure I fully understand the limitation you’re running into.
Based on your description (for example: Action = Modified AND Details contains “index” AND Who ≠ “sqlagent”), this combination of conditions already reflects how Auditor filters are applied today within a single filter set.
Could you please clarify:
In which UI (Search, Reports, Alerts, etc.) you are configuring this filter?
Whether the issue is related to OR logic between rows, grouping, or filter evaluation order?
A screenshot of the filter configuration and the resulting events list would help a lot.
This will help determine whether this is a missing capability, a UX issue, or possibly a misunderstanding of current filter behavior.