You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently message format can be specified like this (in snoopy.ini):
message_format = "ds1=%{datasource1} ds2=%{datasource2:param1,param2}..."
Then only whole message can be filtered, like this:
filter_chain = "exclude_uid:1,2,3;exclude_spawns_of:crond"
It would be splendid if filters could be applied to only specific datasource, right in message format, like this:
message_format = 'ds1:"%{ds1|escape_json_str}" ds2="%{ds2:param1|escape_json_str}"...'
The question that needs to be answered is: do we implement this among existing filters, or do we create new entity class (modifiers, manglers, etc) which does only data mangling.
The text was updated successfully, but these errors were encountered:
Currently message format can be specified like this (in snoopy.ini):
message_format = "ds1=%{datasource1} ds2=%{datasource2:param1,param2}..."
Then only whole message can be filtered, like this:
filter_chain = "exclude_uid:1,2,3;exclude_spawns_of:crond"
It would be splendid if filters could be applied to only specific datasource, right in message format, like this:
message_format = 'ds1:"%{ds1|escape_json_str}" ds2="%{ds2:param1|escape_json_str}"...'
The question that needs to be answered is: do we implement this among existing filters, or do we create new entity class (modifiers, manglers, etc) which does only data mangling.
The text was updated successfully, but these errors were encountered: