-|image2|\r
-| **Filter**\r
-| A filter examine an event and decides if it matches or doesn't. \r
-| Filters are mainly used in rules to decide if the processing entries\r
- should be executed on the given event. They're also used for settings,\r
- and systems like the Graph Correlator re-use Highland Park's filter\r
- mechanism to specify which alarms fit in a correlation. \r
-| The standard library includes a number of simple filters. The Equals\r
- filter, for example, compares a field's value with some other value\r
- and returns true if the values match. \r
-| The standard library also includes filter classes called And, Or, and\r
- Not, so you can compose more complex filters. For example, written in\r
- the standard JSON config format: \r
-\r
-+-----------------------------------------+\r
-| "filter":{ |\r
-| "class":"And", |\r
-| "filters": |\r
-| [ |\r
-| { "class":"Equals", "foo":"abc" }, |\r
-| { "class":"Assigned", "field":"bar" } |\r
-| ] |\r
-| } |\r
-+-----------------------------------------+\r
-\r
-| This filter matches events in which the field "foo" has value "abc"\r
- and the field "bar" is assigned to some value (as opposed to not being\r
- present on the event).\r
-| Filters are used by the consumers to filter out data and consume only\r
- specific set of data which matches the conditions mentioned in filter.\r
-| Filters can be passed as a query parameter by the consumer in consume\r
- request as mentioned below:\r
-| **http://localhost:8080/DMaaP/dmaaprest/events/DMaaP/consumergroup/mHOeNFY4XiWx4CBa?filter=\\{"class":"Equals",\r
- "field":"email", "value":"`test@abc.com <mailto:test@att.com>`__" }** \r
-| Filters can be applied only on data in JSON format i.e. if applied,\r
- filters will automatically ignore any non-json data. \r
-| While consuming, request CONTENT\_TYPE is not relevant to filter.\r
-\r
-The MR API allows a subscriber pass a Highland Park filter as part of\r
-the GET request. This will filter the stream of messages sent back to\r
-the subscriber, but for this to work, there are some requirements: \r
-\r
-- The message payload must be JSON\r
-\r
-- Only a filter built from Highland Park's Standard Library may be\r
- used. (The Cambria API server doesn't have access to plugged in\r
- filters.)\r
-\r
-- The filter must be encoded properly in the URL path.\r
+ |image2|\r
+ \r
+ .. |image2| image:: images/image2.png\r
+ \r
+- **Filter**\r
+\r
+ - A filter examine an event and decides if it matches or doesn't. \r
+ - Filters are mainly used in rules to decide if the processing entries\r
+ should be executed on the given event. They're also used for settings,\r
+ and systems like the Graph Correlator re-use Highland Park's filter\r
+ mechanism to specify which alarms fit in a correlation. \r
+ - The standard library includes a number of simple filters. The Equals\r
+ filter, for example, compares a field's value with some other value\r
+ and returns true if the values match. \r
+ - The standard library also includes filter classes called And, Or, and\r
+ Not, so you can compose more complex filters. For example, written in\r
+ the standard JSON config format: \r
+\r
+ +-----------------------------------------+\r
+ | "filter":{ |\r
+ | "class":"And", |\r
+ | "filters": |\r
+ | [ |\r
+ | { "class":"Equals", "foo":"abc" }, |\r
+ | { "class":"Assigned", "field":"bar" } |\r
+ | ] |\r
+ | } |\r
+ +-----------------------------------------+\r
+\r
+ - This filter matches events in which the field "foo" has value "abc"\r
+ and the field "bar" is assigned to some value (as opposed to not being\r
+ present on the event).\r
+ - Filters are used by the consumers to filter out data and consume only\r
+ specific set of data which matches the conditions mentioned in filter.\r
+ - Filters can be passed as a query parameter by the consumer in consume\r
+ request as mentioned below:\r
+ - **http://localhost:8080/DMaaP/dmaaprest/events/DMaaP/consumergroup/mHOeNFY4XiWx4CBa?filter=\\{"class":"Equals",\r
+ "field":"email", "value":"`test@abc.com <mailto:test@att.com>`__" }** \r
+ - Filters can be applied only on data in JSON format i.e. if applied,\r
+ filters will automatically ignore any non-json data. \r
+ - While consuming, request CONTENT\_TYPE is not relevant to filter.\r
+\r
+ The MR API allows a subscriber pass a Highland Park filter as part of\r
+ the GET request. This will filter the stream of messages sent back to\r
+ the subscriber, but for this to work, there are some requirements: \r
+\r
+ - The message payload must be JSON\r
+\r
+ - Only a filter built from Highland Park's Standard Library may be\r
+ used. (The Cambria API server doesn't have access to plugged in\r
+ filters.)\r
+\r
+ - The filter must be encoded properly in the URL path.\r