When an MSE cloud-native gateway returns HTTP errors such as 404 or 503, the AI diagnostics tool analyzes error logs, identifies the root cause, and recommends a fix. Specify filters such as the error code, domain name, or request path, and the tool returns a diagnosis based on matching log entries.
How it works
The AI diagnostics tool queries the error logs of the cloud-native gateway based on the filters that you specify. It analyzes up to 20 matching log entries to identify the root cause of the HTTP error, and then returns the cause along with a recommended solution.
Prerequisites
Before you begin, make sure that you have:
An MSE cloud-native gateway instance that is running
Access to the MSE console
Run AI diagnostics
-
Log on to the MSE console. In the top navigation bar, select a region.
-
In the left-side navigation pane, choose Cloud-native Gateway > Gateways. On the Gateways page, click the ID of the gateway.
In the left-side navigation pane, click AI Diagnostics.
On the AI Diagnostics page, configure the following filter parameters and select a time range.
NoteOnly the first 20 error logs that match the filters are analyzed per query.
Parameter
Description
Instance
Select the cloud-native gateway instance to diagnose.
Error Code
Enter an HTTP status code such as
404or503, or select a common status code from the list.Domain Name
Select a domain name that is associated with the gateway on the Domain Names page.
Request Path
Enter the request path, such as
/api/v1/users.Routing Rule Name
Select a routing rule to narrow the diagnosis scope.
Request ID
Enter a request ID to diagnose a single request.
Custom Time
Select a time range. Error logs from the past three days are available.
Click Submit.
Review the diagnosis results. The output includes the identified cause and a recommended solution.
Limits
Error logs are retained for three days. Logs older than three days cannot be queried.
Each query analyzes a maximum of 20 matching error log entries.
What to do next
If the diagnosis points to a routing misconfiguration, review and update the routing rules for the cloud-native gateway.
If the diagnosis points to a backend service issue, check the health status and logs of the upstream service.