When application pods run into performance degradation or unexpected failures, you need pod-level resource metrics to pinpoint root causes. Pod monitoring in Enterprise Distributed Application Service (EDAS) provides CPU, memory, network traffic, and network packet metrics for individual pods, so you can identify resource bottlenecks, diagnose issues, and make informed scaling decisions.
Supported editions
Pod monitoring is available in Professional Edition and Platinum Edition only. Standard Edition does not support this feature.
View pod metrics
To view monitoring data for a specific pod, navigate to the Pod Monitoring tab:
Log on to the EDAS console.
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, and then click the Pod Monitoring tab.
Interact with metric charts
All metric charts on the Pod Monitoring tab share the same interactions:
Hover over any data point to view its exact value and timestamp.
Click a legend entry to show or hide the corresponding data series.
Each chart covers the time period selected at the top of the page.
Metric reference
CPU
The CPU section displays cumulative CPU utilization of the pod over the selected time period.
Consistently high CPU utilization suggests the pod needs higher CPU limits. Sustained low utilization indicates over-provisioned resources that you can reclaim.
Physical memory
The Memory section tracks two metrics:
| Metric | Description |
|---|---|
| Memory usage | Actual memory consumed by the pod |
| Memory quota | Memory limit configured for the pod |
When memory usage approaches the quota, the container risks termination with an out-of-memory (OOM) error. Monitor the gap between usage and quota to determine whether to adjust the pod's memory limits.
Network traffic
The Network Traffic (Bytes) section tracks inbound and outbound data volume:
| Metric | Description |
|---|---|
| Received network traffic (bytes) | Total bytes received by the pod |
| Sent network traffic (bytes) | Total bytes sent by the pod |
A sudden spike in either metric can indicate abnormal traffic patterns, such as a traffic surge or a misconfigured client flooding the pod with requests.
Network packets
The Network Packets (Count) section provides granular network health metrics:
| Metric | Description |
|---|---|
| Number of sent network packets | Total number of packets transmitted by the pod |
| Number of discarded network packets among the sent network packets | Packets dropped among sent network packets |
| Number of discarded network packets among the received network packets | Packets dropped among received network packets |
| Number of errors that have occurred when network packets were sent | Errors that occurred when sending packets |
| Number of errors that have occurred when network packets were received | Errors that occurred when receiving packets |
Non-zero drop or error counts typically signal network congestion, resource constraints, or infrastructure issues. Investigate the underlying node and network configuration if these values persist.