The content described in this article is available in meshIQ Control Center versions 12.1 and greater.
For a quick overview of what's new or changed, visit the meshIQ Highlights page for a version-by-version breakdown.
The Audit Report screen displays audit records for actions performed in the Track application (meshIQ Track or Xray). By default, the audit history is displayed in reverse chronological order (starting with the newest record). But you can customize the way in which records are displayed.
The database administrator will need to maintain the audit history.
You see Working with Tables in the Customizing the meshIQ Control Center interface for more information about managing columns.
Select Audit Report > Track Audit Reports to run this report.
Save Report Results
To save results, click the Export Track Audit Records button . You can choose the format for your file: .csv or .json.
A .csv or .json file with a unique file name will automatically download. Example: exported_data_1696952627733.csv or exported_data_1696952695407.json.
The file will contain all data from the report based on any filters that you have applied. By default, results are limited to 25,000 records.
To save the selected records, select them and click on Export Selected... As *.csv or *.json from the Selected menu.
The available columns in the export (CSV or JSON) may vary based on the query or filters applied. The columns listed below are possible columns, but the actual columns included depend on the query or filters used.
| Possible Report Columns | |
|---|---|
| Name | Description |
| LogID | A unique identifier for each log entry in the system. |
| OriganizationName | The name of the organization associated with the log entry. |
| RepositoryID | The unique identifier for the repository where the log entry is recorded. |
| LogType | The category of the log (e.g., error, warning, informational) |
| Token | A unique value or identifier associated with a specific session or transaction. |
| StatementType | Describes the type of action or statement (e.g., SQL query, API call, or system event) recorded in the log. |
| ItemType | The type of item affected by the action. This could be a file, service, or other resource being logged. |
| Severity | Indicates the level of importance or criticality of the event (e.g., critical, high, medium, low). |
| Description | A detailed description of the event or action logged. |
| ReportTime | The timestamp when the report was generated or when the event occurred. |
| StartTime | The timestamp indicating the beginning of the event or action being tracked. |
| EndTime | The timestamp indicating when the event or action ended. |
| ElapsedTime | The total time that the event or action took, calculated as the difference between the start and end times. |
| WaitTime | Time spent waiting during the event, often used in performance audits to measure delays or bottlenecks. |
| UpdateTime | The time at which the log entry was last updated, useful for tracking changes or modifications in logs. |
| Exception | This column would contain information related to any exceptions or errors that occurred during the logged event. |
| Tag | This column is usually used to categorize or label logs for easier identification or filtering. |
| JobID | A unique identifier for a specific job or task associated with the log, helping to correlate logs with specific processes. |
| UserName | User who performed the action in the Track application. |
| ResourceName | The name of the resource (e.g., file, server, service) that was involved in the event being tracked. |
| Message | The actual message or output generated during the logged event, which could include error details, status updates, or other relevant information. |
| Properties | Additional properties related to the log entry. This could include configurations, or other information associated with the event. |
| Statistics | Numerical data or statistics associated with the log entry, like performance metrics or usage data, helping to analyze system performance. |