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

[UXPROD-345] Configuration for Message Queue Created: 05/Mar/18  Updated: 19/Jan/19  Resolved: 19/Jan/19

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: Unassigned
Resolution: Won't Do Votes: 0
Labels: analytics, kafka
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-332 Message Queue for Data Extraction Closed
Epic Link: Reporting: Analytics and Audit Data Logging for External Reporting
Front End Estimate: Very Small (VS) < 1day
Front End Estimator: VBar
Back End Estimate: Medium < 5 days
Back End Estimator: VBar
Development Team: EBSCO - FSE

 Description   

Implement configuration support for the Kafka message queue.

This is a system-level configuration that won't be exposed through Folio Settings (not end-user accessible). Configuration will be managed with a combination of administrative APIs and static initialization configuration.

  • Hostname / IP for queue
  • Port numbers
  • Kafka configuration settings / parameters (# instances,
  • Zookeeper settings / parameters

See docker-compose.yml in comments to UXPROD-340 Closed



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

Wondering if a command-line parameter is good enough (just like how storage modules get db connection info).

Comment by VBar [ 19/Jan/19 ]

Closing as not needed. There is no need to configure message queues at the tenant level.

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