Split Event 133 by attribute - Access Direction - Read / Write
I’d like to request a feature that allows Event 133 to be split by attribute, separating the Read events (which include numerous files on the USB drive) from the Write events, possibly into 2 different events. The high volume of noise generated by the Read events makes it challenging to parse the data effectively and filter out the unnecessary noise.
Andy Hellsten
shared this idea
Thank you for the feedback and the additional clarification.
Based on the current status, the existing event filtering options appear to address the reported use case, and the additional event filtering is having the desired effect so far.
We will therefore close this idea for now. Should further requirements come up, especially around separate event IDs or additional filtering capabilities for read/write access events, please feel free to submit a new request or provide additional details.