# View Clusters & Cost Trends To explore how your EKS clusters are performing and where your Kubernetes costs are going, start by accessing the **Kubernetes Visibility** section in OneLens. This view gives you a high-level summary of your clusters along with cost, efficiency, and potential savings signals. ## How to Access It 1. **Log in** to your[ OneLens UI](https://app-in.onelens.cloud/). 2. From the **left-hand sidebar**, click on **Kubernetes**. 3. You’ll land on the **Clusters** tab by default—this is where all discovered EKS clusters are listed and analyzed. ## Clusters List The **Clusters** page shows both connected and disconnected clusters discovered via CUR. Here you can see: ### **Key Metrics** At the top of the page, you’ll find aggregated metrics that summarize your Kubernetes usage: * **Cost (Month-To-Date)** – Total EKS cost incurred so far in the current month * **Previous Month Cost** – Total cost from the last completed billing month * **Potential Savings** – Estimated savings based on optimization recommendations from OneLens * **Total Clusters** – The number of EKS clusters currently detected from CUR You can get a quick sense of current cloud spend trends, helping you assess how this month compares with the last and where optimization opportunities may exist. ### **Cluster List Table** You’ll see a table listing all the EKS clusters detected through CUR, enriched with key metadata and metrics that help you assess both cost and operational efficiency. Each row includes: * **Cluster Name** – The name identified through CUR or the OneLens agent * **Version** – The current Kubernetes version * **Status** – Shows the cluster’s connectivity state: * **Connected** – OneLens agent is installed and actively sending data * **Disconnected** – Identified through CUR, but the agent hasn’t been installed yet * **Deleted** – The cluster has been removed from your environment but still appears in the list * **Cost** – Total cost attributed to the cluster for the selected time period * **Potential Savings** – Estimated savings based on inefficiencies and unused resources * **Efficiency** – A derived metric (available only for connected clusters) that reflects how effectively the cluster resources are being utilized relative to cost * **Region** – AWS region where the cluster is or was deployed {% hint style="success" %} ## **NOTE** Clusters marked as **Deleted** have been removed during the current month but still show up because they **incurred costs within the ongoing billing period**. They will automatically be removed from the list after the current month ends. **Hover on the** **delete status** to see the exact date of cluster deletion. {% endhint %} You can **click on any cluster name** in the table to view its **Cluster-Level Breakdown**, where you'll find workload, namespace, and resource-specific insights—available for connected clusters. To learn more about what’s available at the cluster level, visit the [Cluster-Level Breakdown](/observe-visibility-and-insights/service-cost-monitoring/kubernetes-visibility/cluster-level-breakdown.md) page.
{% hint style="info" %} ## NOTE The data in this section is fully powered by CUR by default. If you’d like to view data from the **OneLens agent** wherever it's available—such as real-time breakdowns by namespace, workload, and labels—**toggle the data source switch** at the top-right corner of the page. {% endhint %} ## Cost Analyzer The **Cost Analyzer** tab gives you a breakdown of how your EKS costs are distributed across clusters, workloads, namespaces, and more. It functions just like the main **Cost Analyzer** tab in OneLens, but with a limited set of features tailored specifically for Kubernetes environments. {% hint style="warning" %} ### Prerequisites To view meaningful data on this page: * Your CUR data must include **EKS split cost allocation** Not sure if split cost allocation is enabled? Visit the [Enable Split Cost Allocation for EKS](/integrations/kubernetes/enable-split-cost-allocation-for-eks.md) guide. {% endhint %}
{% tabs %} {% tab title="Controls" %} Customize your view using the following: * **Date Range** – Select the period you want to analyze * **Granularity** – Choose the time resolution (e.g., daily) * **Filters** – Narrow the view by cluster, namespace, workload type, workload name, labels, charge type, or resource type. * **Group By** – Choose how to segment the cost data across: * Cluster Name * Namespace * Workload Type * Workload Name * Labels * Resource Type * Charge Type {% endtab %} {% tab title="Key Metrics" %} You’ll find two primary metrics: * **Total Cost** – Aggregated EKS cost for the selected filters and period * **Cost Delta** – Change in cost compared to the previous time window {% endtab %} {% tab title="Cost Trend Graph" %} The graph helps you visualize how cost evolves over time across the selected grouping. You can toggle between two visualization styles: * **Bar Chart** – Ideal for distinct comparisons across groupings * **Area Chart** – Useful for viewing accumulated or stacked trends If you prefer a focused view on tabular data, you also have the option to **hide the graph** entirely. {% endtab %} {% tab title="Detailed Table" %} A tabular breakdown appears below the graph, giving you a structured view of cost by the selected grouping. {% hint style="success" %} ## **Highlight** You can **toggle the cost delta display** to view it as either: * **Dollar ($)** value * **Percentage (%)** change {% endhint %} The table can also be **exported** for offline use or reporting. You can choose from: * **CSV** – Ideal for detailed data analysis and manipulation. * **Excel** – Provides a structured spreadsheet version of the report. {% endtab %} {% endtabs %} ## What to Explore Next Dig into specific workloads or namespaces using the [Cluster-Level Breakdown](/observe-visibility-and-insights/service-cost-monitoring/kubernetes-visibility/cluster-level-breakdown.md) page. --- # 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/view-clusters-and-cost-trends.md?ask= ``` 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.