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

[UXPROD-1221] Implement support for AES Message Stream Creation Created: 03/Oct/18  Updated: 15/Mar/22

Status: In Review
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: Unresolved Votes: 0
Labels: analytics, transactdata
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UXPROD-343 Partition Transactions into Kafka Topics Closed
Relates
relates to UXPROD-1446 Fomalization of AES Message Streams Open
relates to UXPROD-1222 Implement Message Stream Filters Closed
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   

This is implementation of the process to define AES message streams. These are defined programmatically from Message Stream Descriptors (YAML). The function is the responsibility of the AES Message Stream Registration component.

  • An AES Message Stream Descriptor is provided, validated and parsed.
  • Upon success, a Message Stream is created in storage
  • Tenant context is identified and stored a separate metadata

The result will be an active Message Stream definition that is accessible to the AES Mesage Stream Processor at runtime.



 Comments   
Comment by Hongwei Ji [ 03/Dec/18 ]

As discussed today, the AES message stream descriptor will be postponed. For now, the message filter rules work ( UXPROD-1222 Closed ) is sufficient to dispatch messages to different targets.

Comment by VBar [ 19/Jan/19 ]

As part of split, moving this story to newly created UXPROD-1446 Open feature

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