The Application Overview page gives you a single view of your Java application's health in SAE — request volume, response time, garbage collection (GC) activity, slow SQL queries, and dependency performance — so you can identify problems without switching between tools.
SAE integrates with the Application Monitoring sub-service of Application Real-Time Monitoring Service (ARMS), an application performance management (APM) service. Enabling monitoring requires only installing the ARMS agent — no code changes. The agent identifies slow or abnormal API operations, captures request parameters, and pinpoints system bottlenecks to speed up troubleshooting.
Open the Application Overview page
Log on to the SAE console. In the left-side navigation pane, choose Applications > Applications. Select a region in the top navigation bar and a namespace from the Namespace drop-down list, then click the application name.
In the left-side navigation pane, choose Application Monitoring > Application Overview. On the Application Overview page, view the Overview tab.
Metrics on the Overview tab
The Overview tab organizes metrics into four groups.
Summary metrics
At the top of the page, you see totals for the selected time range, with day-on-day and week-on-week comparisons:
| Metric | What it tells you |
|---|---|
| Total requests | Overall traffic volume; a sudden drop may indicate a deployment issue or upstream failure |
| Average response time | Baseline latency; a rising trend often points to slow database queries or downstream dependencies |
| Instances | Number of running instances; check this alongside response time to determine whether scaling is needed |
| Full GC events | Java Virtual Machine (JVM) garbage collection activity; frequent full GCs can degrade throughput and indicate heap sizing issues |
| Slow SQL queries | Database queries exceeding the response threshold; a spike here usually explains a response time increase |
Application Events
The Application Events section shows a timeline of events that may affect availability, including:
Availability alerts — triggered by deadlocks, out-of-memory (OOM) errors, or application startup events
Application monitoring alerts — threshold breaches detected by ARMS
Kubernetes cluster events — infrastructure-level events from the underlying cluster
Hover over a column in the chart to view the event list at that point in time. For details on configuring alerts, see Event center.
Application Support Services
This section shows time series curves for the services your application exposes to other callers: request volume and average response time per service. Use these curves to identify which of your endpoints is receiving the most traffic or experiencing the highest latency.
Application Dependent Services
This section shows time series curves for the external services your application calls: request volume, average response time, instance count, and HTTP status codes. If you see 5xx status codes or rising latency in a dependent service, the issue is likely upstream — not in your application code.
