Audit page
Repository / Application database > Audit > Audit
Purpose of the page¶
This page allows access to the log report, see changes and identifyany errors.
Buttons and/or links on the page
| Element | Description |
|---|---|
| (only in the Repository) Allows you to: - store offline the operations present in the auditing trace - delete the operations present in the auditing trace - delete the operations present in the log of the auditing trace The user must specify : - the criterion for the definition of the date the system will use to filter the data to be deleted or archived. The possible values are: - Relative. the reference date is calculated by the system starting from today and then going back the number of days specified by the user (# Days up to today); - Absolute. The reference date is specified by the user (Specific date). In both cases, the system works on the information present in the audit log with the date before or equal to the reference date. - a filter on the operation type so as to partialize the data present in the audit log to be deleted based on the operation type. . These data processes can also be scheduled. Offline data can be consulted via the functionality accessible from the web interface of the administrator user by following this path: Repository > Audit > Audit , then click on | |
| - Details: opens the selected operation’s details page. - Details of all parts: for operations split into several parts, it groups the activities into the relative parts and shows the details. - Merged details: for operations split into several parts, this shows all the activities inherent to an operation. - Metadata log report: opens the "Metadata log report" page relating to the selected data processing (currently only available for the"DB update: Element lists update" data processing). The report page will display a grid with details of deleted, inserted and updated element lists as a result of the data processing launch - (only if the licence includes Machine Learning module) Download ML log details: by selecting an operation with one of the following descriptions: Train ML processing, Execute ML data processing, Execute a JOB, Financial Reporting: Run data processing by form, Data processing started, you can download the .zip file containing the log files relating to the each Train or Execute ML data processing performed. In the event that no log file is available for the selected data processing or the service cannot be accessed at that time, an error message will be displayed. | |
| - Online: updates the data in real time - Archived: shows the archived data |
Information on Logs
| Element | Description |
|---|---|
| Result | Operation outcome: - : completed successfully - : completed successfully, but with warnings - : failed |
| Date | Date and time activity started |
| Operation type | Operation logged by the system. |
| Part | Part of the data process (if split). |
| Data processing / Managed data | Only for management operations. Indicates the table of the database involved. |
| JDBC statistics | Information on SQL queries run by the operation. - n: total queries run - t: total run time - M: longest query run time - P: database time as a percentage of total time |
| Mode | Operation start mode |
| Concurrency level | Maximum number of simultaneous data processes |
| OID | Unique ID of the operation |
| Correlation OID | Unique ID of a group of operations. Useful for data processes made up of several parts. |