Enhance error notifications with detailed information and expand the administration page to allow downloading Process Mining logs directly from the GUI.

Why is it useful? 

Currently, IBM Process Mining users often encounter generic error messages (e.g., "Generic Error") when issues arise during data uploads, process analysis, or monitor execution. These messages provide little insight into the root cause, making troubleshooting difficult and time-consuming. Additionally, accessing logs for deeper analysis typically requires technical intervention or navigating complex backend systems (such as OpenShift or Kubernetes pods), which is not feasible for most business users or process analysts.

Who would benefit from it?

• Process Analysts and Business Users: Providing detailed error messages would enable them to quickly identify and resolve issues without relying on IT support, thereby reducing downtime and improving productivity.
• Administrators and IT Teams: Direct access to logs via the administration page would streamline diagnostics, accelerate issue resolution, and reduce the need for manual log collection from pods or servers.
• Support Teams: More descriptive error notifications and easy log access would enable faster, more accurate troubleshooting and reduce the back-and-forth required to gather diagnostic data.

How should it work?

Detailed Error Notifications:

• Replace generic error messages with specific, actionable information (e.g., "Failed to upload event log: Column 'OrderID' is missing or contains invalid data. Expected format: alphanumeric, max 20 characters").
• Include links to relevant documentation or suggested fixes within the error notification.
• Allow users to copy error details to clipboard for easy sharing with support teams.

Expanded Administration Page:

• Add a "Logs" section to the administration page, where users can view, filter, and download logs for their projects or the entire organization.
• Provide options to download logs in standard formats (e.g., .txt, .json, or .zip) for further analysis or to attach to support tickets.
• Implement role-based access to ensure only authorized users (e.g., administrators) can download logs, maintaining security and compliance.

Integration with Monitors and Alerts:

• When monitors or automated alerts detect process deviations or errors, include relevant log snippets or error codes in the notifications to provide immediate context.

Considerations:

• Ensure that log files are anonymized or redacted as needed to protect sensitive information.
• Allow users to specify time ranges or log levels (e.g., INFO, WARNING, ERROR) to download only the most relevant data.
• Maintain an audit trail of log downloads for governance and compliance purposes.