RFE - Server-Side Logging for AAI Web UI and API Errors

Products

• Automation Analytics & Intelligence

Issue/Introduction

When users encounter errors within the Automic Automation Intelligence (AAI) Web UI—such as a "400 Bad Request" when saving a jobstream alert—the diagnostic details are not captured in the server-side jaws.log.

Currently, troubleshooting these issues requires Support to request that customers use browser developer tools (Network tab) to reproduce the behavior and export a HAR file. This process increases operational friction and delays the Time-to-Resolution (TTR).

Environment

Product: Automic Automation Intelligence (AAI) 

Version: All Versions (Prior to implementation of F66070) 

Component: Web UI / API

Cause

The current AAI backend logging framework does not have a mechanism to intercept and record front-end Web UI or API communication error responses into the centralized server logs.

Resolution

This issue is addressed via a Request for Enhancement (RFE), which has been reviewed and accepted by AAI Product Management.

Enhancement Tracking Details:

• Feature ID: F66070
• Internal Tracking: DE203666
• Description: Enhance the backend logging framework to record detailed Web UI and API error responses directly into jaws.log or a dedicated server-side log file.

Expected Functionality: Once implemented, server logs will include diagnostic context for UI/API failures, including:

• Endpoint URLs
• Request Payloads
• HTTP Response Codes

Workaround: Until the enhancement is released in a future version of AAI, continue to use browser developer tools to capture HAR files for any Web UI-specific anomalies:

1. Open Browser Dev Tools (F12).
2. Navigate to the Network tab.
3. Reproduce the error.
4. Right-click and select "Save all as HAR with content."
5. Attach the HAR file to the support case.