Summary

As an administrator,
I want to remove fields from log messages that I believe are extraneous
so the message is smaller

Acceptance Critiera

• Verify the collector pruns fields for log messages that have a field which matches the spec
• Verify the collector keeps fields and prunes all others when the filter specs both 'in' and 'notIn'
• Verify the collector leaves log messages unchanged if the record does not contain the matching spec
• Verify filters only accept "in/notIn" fields that contain valid path expressions including [a-ZA-Z0-9._]. Any other path segment outside the characters must be quoted [/-] etc.
• Verify CLF provides status when filters are invalid
• Verify upstream repo includes feature documention and updated feature matrix

Notes

• Check enhancement to confirm it explicitly states order of precedence when a field exists in both 'in' and 'notIn'