# Cost & Node Analysis

## Overview

When you need a closer look into how your Kubernetes clusters are driving cost and efficiency, the **Cost & Node Analysis** section brings everything into focus. The analysis helps you break down cost drivers at the nodes level and evaluate how effectively your nodes are being utilized.

The page consists of two tabs: **Cost Analysis** and **Node Analysis**, each offering a distinct lens into your infrastructure.

## Cost Analysis

In the *Cost Analysis* tab, you're presented with a breakdown of costs specific to the cluster you're viewing. It carries the same intuitive layout as the broader [View Clusters & Cost Trends](/observe-visibility-and-insights/service-cost-monitoring/kubernetes-visibility/view-clusters-and-cost-trends.md#cost-analyzer) in Kubernetes Visibility, but here, your focus is narrowed to a single cluster.

You can see how costs are split across compute, storage, and networking within the cluster. Use familiar groupings and filters to drill into trends and identify shifts in cluster-level spend.  You get to stay proactive in managing cost surges before they become expensive problems.

<figure><img src="/files/KwPP9LPbyS84xk0hnx3N" alt="" width="563"><figcaption></figcaption></figure>

## Node Analysis

The *Node Analysis* tab is where you evaluate how well your underlying compute nodes are performing—both financially and operationally. Whether you’re trying to find underutilized nodes or validate the impact of your spot instance strategy, here you get all the data you need in one place.

### Key Metrics

Right at the top, you’ll find essential metrics that give you a snapshot of your node performance:

* **Total Compute Cost** – See what you're spending to run all nodes within the cluster.
* **Node Efficiency** – Understand how well you're utilizing provisioned CPU and memory cost.
* **Unused Cost** – Identify the portion of your spend that went to idle resources.
* **Spot Usage Cost** – Track the cost saved through your spot instance strategy.

  <figure><img src="/files/lNLRslmujZdLloraDvaO" alt="" width="563"><figcaption></figcaption></figure>

## Node Overview Table

Dig into each node’s performance and cost with the overview table. It’s designed to help you compare and group nodes effortlessly.

<details>

<summary>List of Columns</summary>

| Column                  | Description                                                                     |
| ----------------------- | ------------------------------------------------------------------------------- |
| **Group by Node Group** | Toggle this to organize the data by node groups for clearer analysis.           |
| **Node Type**           | Displays the instance type (e.g., `m5.large`, `c6g.xlarge`) used by the node.   |
| **Compute Hours**       | Shows the total number of hours each node has been active.                      |
| **Cost**                | Reflects the actual cost incurred by each node.                                 |
| **Efficiency**          | Highlights how effectively the node's resources are being utilized.             |
| **Spot Cost**           | Indicates the cost specifically incurred from using spot instances.             |
| **Spot Coverage %**     | Represents the percentage of the node's runtime that was covered by spot usage. |

</details>

<figure><img src="/files/HktipwVD01zn1EzkmzqD" alt="" width="563"><figcaption></figcaption></figure>

You can use this table to identify over-provisioned nodes, validate the balance between spot and on-demand usage, and plan more efficient resource distribution.

## Utilization Trend

The *Utilization Trend* section gives you visual insights into how CPU and memory are used over time—enabling quick identification of inefficiencies.

#### **CPU Utilization**

You can compare **CPU utilized**, **CPU unused**, and **p99 CPU utilization** against the total CPU hours. This makes it easier to identify whether certain nodes are being over- or under-utilized, and where right-sizing could cut costs.

#### **Memory Utilization**

In a similar view, track your **used** vs **unused** memory, helping you spot memory over-allocation early.

<figure><img src="/files/o5tLeOXbdksTEKyFk5aC" alt="" width="563"><figcaption></figcaption></figure>

## Spot vs On-Demand Usage Cost Trend

The following trend chart shows how your costs are split between **spot** and **on-demand** nodes over time. By following this graph, you can evaluate how well you're balancing cost savings with workload reliability. If spot coverage is too low, this view makes it clear—prompting you to consider opportunities for optimization.

<figure><img src="/files/p05JZ60cxc7aQhr90nLa" alt="" width="563"><figcaption></figcaption></figure>

## What’s Next?

Once you've explored how your nodes contribute to cost and performance, you can move to the [Workload Drilldown](/observe-visibility-and-insights/service-cost-monitoring/kubernetes-visibility/workload-drilldown.md) page to see how individual namespaces and deployments are utilizing those resources.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.onelens.cloud/observe-visibility-and-insights/service-cost-monitoring/kubernetes-visibility/cost-and-node-analysis.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.