Closed aq94 closed 2 years ago
aq64
Thanks for raising this issue and the detailed description.
Gaps in audit coverage between i2:Notebook and i2:ANBP would not be anticipated. I will spin up a test suite and validate the behaviour and plan next steps from here.
Steve
aq94
A brief update. The test harness has similar outcomes. Discussing further tomorrow.
Steve
Thanks Steve, will keep an ear out and double check from our end to see if there are any other discrepancies to note.
Cheers
Seeing as there haven't been any updates on this issue I'm closing it for now, but feel free to re-open with any new information.
Thanks Colvin this was resolved via Cases/L3 escalation APARS etc.
Hi there,
Our team has recently upgraded from EIA 2.3 to EIA 2.4.1 in one of our dev environments and following this we have followed the steps outlined in the links below to implement and configure audit logging (to database).
https://github.com/IBM-i2/analyze/blob/master/documentation/Preparing-to-use-IBM-i2-Analyze-Developer-Essentials.md https://github.com/IBM-i2/analyze/blob/master/documentation/Configuring-the-audit-logging-to-database-example-project.md
We have completed these steps and now have an I2AUDIT schema and the four tables (EXPAND, QUICK_SEARCH, RECORD_RETRIEVAL and VISUAL_QUERY). Note that instead of creating a new AUDIT database, we have created the schema and tables within our dev environment ISTORE. We have also not performed step 7 in the second link relating to 'Debugging Developer Essentials in Eclipse'
The tables are capturing some log activity with some issues. Please see below for a summary:
I2AUDIT.EXPAND
I2AUDIT.QUICK_SEARCH
I2AUDIT.RECORD_RETRIEVAL
I2AUDIT.VISUAL_QUERY
Are there any known fixes for the issues discussed above? Let me know if there are any other details required from our side.
Thanks
GitHub Ticket Issues.xlsx