Nodes Tab
Nodes Tab
#380
The Nodes report provides utilization details of the individual nodes that are part of node group. You can see key metrics including both peak and average utilization for both CPU and memory. These metrics highlight container performance and stability issues.
Figure: Nodes Tab
More significantly, you can now see the pods as a percentage of the maximum allowed on a node and identify where nodes are unable to host more pods, due to the maximum CPU and /or memory value being too low. i.e. a virtual constraint.
Figure: Node Details
You can create filters at the column or table level. See Using Table Column Features.
Two system views provide commonly used reports:
- Inventory—This view focuses on the number and type of nodes in your environments.
- Utilization—This view shows how effectively the nodes are used.
Figure: Node System Views
The node report provides the following details:
Table: Node Details Table
|
Column |
Description |
|---|---|
|
Cluster |
The cluster name containing the selected node group/nodes. |
|
Node Group |
The name of the node group that contains the selected node. For nodes that do not belong to a node group, the node group value should be <cluster-name>-default” |
|
Node |
The node name. |
|
Instance Type |
The node's instance type. In cases where the instance type cannot be determined (i.e. bare-metal, private cloud environments) the primary node type is indicated as: CPU x memory size, e.g. 8x16. A dash (-) indicates that the node instance details could not be determined. |
|
CPU Utilization - Avg (%) |
The average CPU utilization for this node, during the past 7 days of history. The cell will be shaded when the value exceeds 90%. |
|
CPU Utilization - Peak (%) |
The maximum CPU utilization for this node, during the past 7 days of history. The cell will be shaded when the value exceeds 90%. |
|
Memory Utilization - Avg (%) |
The average memory utilization for this node, during the past 7 days of history. The cell will be shaded when the value exceeds 90%. |
|
Memory Utilization - Peak (%) |
The maximum memory utilization for this node, during the past 7 days of history. The cell will be shaded when the value exceeds 90%. |
|
Node Hours |
The total number of hours that this node has been up and running, based on CPU utilization, during the past 7 days of history. |
|
Age (days) |
The number of days since the node was first discovered by Densify. |
|
First Seen Date |
The date, on which this instance was first discovered by Densify. |
|
Last Seen Date |
The date, on which this instance last had CPU utilization data collected by Densify. |
|
Max Allowed Pods |
The optimal configuration for the maximum number of pods allowed on this node. |
|
No. of Pods - Avg |
The average number of pods running on this node during the past 7 days of history. |
|
No. of Pods - Peak |
The maximum number of pods running on this node during the past 7 days of history. |
|
Pods (% of Max Allowed) |
The ratio of the maximum number of pods that were run versus the maximum that the node could support, in the last 7 days. Calculated as the (peak number of pods)/(maximum allowed pods). The cell will be shaded when the value exceeds 90%. |
|
Node CPU |
The total number of CPUs on this instance type. |
|
Allocatable CPU (cores) |
The number of CPUs that can be allocated to pods. |
|
Node Memory (GB) |
The total amount of memory configured on this instance type. |
|
Allocatable Memory (GB) |
The amount of memory that can be allocated to pods. |
Please observe the following for this set of data:
- Missing data is indicated with a dash (-).
Workload charts at the bottom of the page, show hourly min/max and sustained activity for the selected node. See Using the Workload Charts for details of using the chart features to review detailed node utilization.
See the following topics for details of the other views: