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: | VBar |
| 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 | ||||||||
| Front End Estimator: | VBar | ||||||||
| Back End Estimate: | Medium < 5 days | ||||||||
| Back End Estimator: | VBar | ||||||||
| Development Team: | EBSCO - FSE | ||||||||
| Description |
|
Optimization iteration of the AES Message Processor. The goal is to reduce amount of transaction data to be pushed to the Message Queue. Folio transactions are chatty. For a given operation several REST interfaces may be invoked to fullfill the request. For example, before calling a requested interface, mod-permissions may be first called to verify authorization. From the point of view this is one operation and it should be captured as a single Transaction. The additional calls to permissions do not convey any useful additional information for the purposes of analytics. |
| Comments |
| Comment by Hongwei Ji [ 03/Dec/18 ] |
|
As discussed today, it is technically challenging to buffer requests per transaction and detect potential redundant requests due to the fact that there could be multiple mod-aes modules behind one single load balancer. Also, storage is cheap so it is not really necessary to remove redundant requests from economic perspective. Last, the redundant info can be handled/filtered at the later reporting/analytic phase. |
| Comment by VBar [ 18/Jan/19 ] |
|
Close as not needed at this time. |