> For the complete documentation index, see [llms.txt](https://docs.perfectscale.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perfectscale.io/visibility-and-optimization.md). # Visibility & Optimization - [Clusters' metrics overview](https://docs.perfectscale.io/visibility-and-optimization/clusters-metrics-overview.md): Overview provides advanced visibility to the most important metrics per each cluster, allowing you to prioritize which cluster needs to focus on - [Podfit | vertical pod right-sizing](https://docs.perfectscale.io/visibility-and-optimization/podfit-or-vertical-pod-right-sizing.md): Explore a granular, comprehensive view of your clusters' health and costs, identify and prioritize areas that need attention while autonomously optimizing workloads - [Understanding 'At Risk' indicators](https://docs.perfectscale.io/visibility-and-optimization/podfit-or-vertical-pod-right-sizing/understanding-at-risk-indicators.md): Explore wide range of 'At Risk' indicators that PerfectScale provides - [LimitRange and ResourceQuota](https://docs.perfectscale.io/visibility-and-optimization/podfit-or-vertical-pod-right-sizing/limitrange-and-resourcequota.md): This page explains how PerfectScale handles LimitRange and ResourceQuota in your clusters, ensuring compliance with your specified resource allocation constraints - [Muted workload](https://docs.perfectscale.io/visibility-and-optimization/podfit-or-vertical-pod-right-sizing/muted-workload.md): Understand the impact of muted workloads on various metric calculations - [Infrafit | node right-sizing](https://docs.perfectscale.io/visibility-and-optimization/infrafit-or-node-right-sizing.md): InfraFit is an advanced feature that provides a granular view of resource allocation across the various nodes supporting your Kubernetes clusters - [Node group view](https://docs.perfectscale.io/visibility-and-optimization/infrafit-or-node-right-sizing/node-group-view.md): Gain insights and identify the most impactful optimization opportunities within the node groups - [Node type view](https://docs.perfectscale.io/visibility-and-optimization/infrafit-or-node-right-sizing/node-type-view.md): Explore the node type view of Infrafit - [GPU optimization](https://docs.perfectscale.io/visibility-and-optimization/gpu-optimization.md): Reduce cloud GPU costs with real-time utilization visibility and insights - [Java containers](https://docs.perfectscale.io/visibility-and-optimization/java-containers.md): Optimize Java containers with granular visibility and tailored recommendations - [Karpenter optimization](https://docs.perfectscale.io/visibility-and-optimization/karpenter-optimization.md): Maximize Karpenter efficiency with granular visibility and data-driven recommendations - [Trends monitoring](https://docs.perfectscale.io/visibility-and-optimization/trends-monitoring.md): Unlocks granular visibility and in-depth insight into costs, waste, and risk metrics over time --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.perfectscale.io/visibility-and-optimization.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.