When an application instance returns unexpected errors or HTTP status code spikes, you need a fast way to identify error patterns and trace individual failures. Error analysis aggregates error counts, breaks down HTTP status codes over time, and links each error to its distributed trace, so you can move from symptom to root cause without switching tools.
Prerequisites
Before you begin, make sure that you have:
An EDAS application deployed on a Kubernetes cluster
EDAS Professional Edition or Platinum Edition (Standard Edition does not support error analysis)
Open the error analysis page
Log on to the .
In the left-side navigation pane, choose Application Management > Applications.
In the top navigation bar, select a region. In the upper part of the page, select a microservice namespace.
From the Cluster Type drop-down list, select Kubernetes Cluster.
Click the application name in the Application Name column.
In the left-side navigation pane of the application details page, choose Monitor > Instance Details.
In the left-side pane of the Instance Details page, select the instance to inspect, then click the Error Analysis tab on the right side of the page.
Page layout
The Error Analysis tab is divided into three sections, from top to bottom:
| Section | Description |
|---|---|
| Errors | Time series chart of total error counts for the selected instance |
| HTTP - Status Code | Time series chart that breaks down responses by HTTP status code |
| Error list | Table of all individual errors recorded during the selected time range |
The following sections describe each area and the available interactions.
Error statistics
The Errors section displays a time series chart of total error counts for the selected instance over a given time range.
To explore the data:
Hover over the chart to view error counts at specific points in time.
Click and drag across the chart to zoom in on a specific time range.
Click the
icon to compare error trends across different dates or view data for a custom time period.
HTTP status code statistics
The HTTP - Status Code section displays a time series chart that breaks down responses by HTTP status code. Each status code appears as a separate line, so you can spot spikes in specific error codes such as 404 or 500.
To explore the data:
Hover over the chart to view the count for each status code at a specific point in time.
Click and drag across the chart to zoom in on a specific time range.
Click a status code in the legend to show or hide that series.
Click the
icon to compare trends across different dates or view data for a custom time period.
Error list
The error list shows all individual errors recorded for the selected instance during the specified time range.
To trace a specific error, click the trace ID in the TraceId column to open the full distributed trace for that error.