The root config type for the Highly Efficient Record Processor (HERP) filter configuration file. This ID will be the SLF4j logger target, it can be used in the backend logger configuration to direct it's output to an appender. See the log4j documentation as for how to do this. This ID will be the SLF4j logger target, it can be used in the backend logger configuration to direct it's output to an appender. See the log4j documentation as for how to do this. This string will be used in logging to describe the service being accessed. This string will be used in logging to note the region of the service. This string will be used in logging to note the data center of the service. This is the Handlebars or Mustache based template that will be used to output events. Supported fields include guid, serviceCode, region, dataCenter, timestamp, requestMethod, requestURL, requestQueryString, targetHost, parameters, userName, impersonatorName, projectID, roles, userAgent, responseCode, responseMessage, clusterId, nodeId, requestorIp. A number of helpers are available for formatting for cadf including cadfOutcome, cadfTimestamp, cadfMethod. Indicates whether or not to replace a newline sequence (i.e. \r, \n, \r\n) plus any following whitespace with a single space. This is the set of criteria applied to the events to determine if an event is sent through to the named post filter logger. Multiple FilterOut elements are logically OR'd together. This is an individual criterion used in determining if an event passes through. Multiple Match elements are logically AND'd together. This is the event field to compare the regular expression against. This is the regular expression to apply to the event field.