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

[UXPROD-380] Configuration setting for Audit facility Created: 05/Mar/18  Updated: 17/Jan/19  Resolved: 17/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: Hongwei Ji
Resolution: Done Votes: 0
Labels: auditing, mandatory, vbar1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by UXPROD-1222 Implement Message Stream Filters Closed
Relates
relates to UXPROD-1063 Folio auditing functionality via the ... Closed
Epic Link: Reporting: Analytics and Audit Data Logging for External Reporting
Front End Estimate: Large < 10 days
Front End Estimator: VBar
Back End Estimate: Large < 10 days
Back End Estimator: VBar
Development Team: EBSCO - FSE

 Description   

Implements configuration options as they relate to a particular auditing stream:

  • Where stream will be stored
  • Tenant context
  • Enable/Disable audit stream
  • Data characteristics that define which events to include


 Comments   
Comment by Cate Boerema (Inactive) [ 26/Apr/18 ]

VBar, I need to tag this with a project. Is it Analytics, GDPR, something else?

Comment by Hongwei Ji [ 17/Jan/19 ]

Is this similar to UXPROD-1222 Closed . The routing rules specify what events to capture and which topic to send to. The configuration is tenant specific so have tenant context. Enable/disable can be done through module enable/disable (or by define rules in mod-config).

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