Reporting: Analytics and Audit Data Logging for External Reporting (UXPROD-330)

[UXPROD-1219] Implement Interim post- filter for data Queue Created: 01/Oct/18  Updated: 15/Oct/18  Resolved: 05/Oct/18

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, kafka, reporting
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-333 Okapi Service / Monitor to Extract Tr... Open
relates to MODAES-1 Revive POC work - Okapi pre/post filt... Closed
relates to UXPROD-332 Message Queue for Data Extraction Closed
relates to UXPROD-340 SPIKE: Prototype Kafka Message Queue Closed
Epic Link: Reporting: Analytics and Audit Data Logging for External Reporting
Back End Estimate: Medium < 5 days
Development Team: EBSCO - FSE

 Description   

Create an Okapi post- filter handler for the purposes of capturing all transaction data from Okapi for the purposes of building a Data Lake.

This is considered interim until a decision is made for the Asynchronous Event Service (AES).
Consequently, this post- filter may eventually be refactored as an internal Okapi module.

The filter will capture all transactions and pass the to the message queue ( UXPROD-340 Closed )



 Comments   
Comment by Hongwei Ji [ 15/Oct/18 ]

We have done similar during the data capture POC. So what I did was to clean up the old code and removed irrelevant pieces (RabbbitMQ, MongoDB and PostgreSQL) and checked into a new repo named mod-aes. Tested with a Kafka environment and can see FOLIO traffic is captured as messages in Kafka. Mark this ticket as complete.

Generated at Fri Feb 09 00:13:45 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.