Reporting: Analytics and Audit Data Logging for External Reporting
(UXPROD-330)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Reporting: Analytics and Audit Data Logging for External Reporting |
| Type: | Story | Priority: | P3 |
| Reporter: | VBar | Assignee: | Hongwei Ji |
| Resolution: | Done | Votes: | 0 |
| Labels: | analytics, transactdata | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||
| Epic Link: | Reporting: Analytics and Audit Data Logging for External Reporting | ||||||||||||||||||||||||||||
| Back End Estimate: | Medium < 5 days | ||||||||||||||||||||||||||||
| Back End Estimator: | VBar | ||||||||||||||||||||||||||||
| Development Team: | EBSCO - FSE | ||||||||||||||||||||||||||||
| Description |
|
Provide the ability to filter (select) transaction for AES Message Streams. The functionality belongs in the AES Message Stream Processor component. The selection criteria consist of a single Boolean expression that will include (or exclude) individual transactions based on what they match to.
The initial implementation will support exact matching only and stemming. Stemming (a.k.a “begins with”) is used to match module or version names, while excluding the version numbers that exist on the tail of the string. For example, `“folio_search-*”` will match `“folio_search-1.1.100088”`. Later versions may introduce support for regular expression matching. |
| Comments |
| Comment by Hongwei Ji [ 03/Dec/18 ] |
|
As discussed today, the Stream Filters will be implemented as {"criteria":"some json path", "target":"some Kafka topic name"}
and stored in mod-config. The mod-aes will retrieve (and refresh periodically) the filter rules from mod-config and dispatch messages as defined by filter rules. |