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: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | analytics, kafka | ||
| 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 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.
See docker-compose.yml in comments to
|
| 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. |