From e732d05cd53070f17a0badb79f9c38172d812615 Mon Sep 17 00:00:00 2001 From: andersonid Date: Mon, 29 Sep 2025 21:07:56 -0300 Subject: [PATCH] =?UTF-8?q?Fix:=20esclarecido=20que=20Top=20Resource=20Con?= =?UTF-8?q?sumers=20mostra=20REQUESTS,=20n=C3=A3o=20consumo=20real?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- app/static/index.html | 42 ++++++++++++++++++++++++++++-------------- 1 file changed, 28 insertions(+), 14 deletions(-) diff --git a/app/static/index.html b/app/static/index.html index ba3639b..a5d78c8 100644 --- a/app/static/index.html +++ b/app/static/index.html @@ -1405,7 +1405,7 @@
-

📊 Resource Consumption ❓

+

📊 Resource Consumption (Requests) ❓

CPU ❓

@@ -1432,7 +1432,7 @@
-

🥇 Top Resource Consumers ❓

+

🥇 Top Resource Request Consumers ❓

@@ -2727,21 +2727,28 @@ ` }, 'resource-consumption': { - title: 'Resource Consumption - CPU & Memory Usage', + title: 'Resource Consumption (Requests) - CPU & Memory Requests', content: `
-

Resource Consumption shows how much CPU and memory your cluster is using compared to its total capacity.

+

Resource Consumption (Requests) shows how much CPU and memory your cluster is requesting compared to its total capacity.

What you see:

    -
  • CPU Bar: Shows CPU usage vs. capacity
    • -
  • Memory Bar: Shows memory usage vs. capacity
    • -
  • Overcommit %: How much you're over-allocating resources
    • +
  • CPU Bar: Shows CPU requests vs. capacity
    • +
  • Memory Bar: Shows memory requests vs. capacity
    • +
  • Overcommit %: How much you're over-allocating resources based on requests
    • +
+ +

Important distinction:

+
    +
  • Requests ≠ Usage - This shows what pods are configured to request, not actual consumption
    • +
  • Planning tool - Helps understand resource allocation planning
    • +
  • Configuration-based - Based on pod specifications, not real-time metrics

Reading the bars:

    -
  • Green: Safe usage levels
    • +
  • Green: Safe request levels
  • Yellow: Moderate usage, monitor
  • Red: High usage, take action
@@ -2793,21 +2800,28 @@ ` }, 'top-consumers': { - title: 'Top Resource Consumers - Biggest Users', + title: 'Top Resource Request Consumers - Who Requests Most Resources', content: `
-

Top Resource Consumers shows which applications are using the most CPU and memory resources.

+

Top Resource Request Consumers shows which applications are requesting the most CPU and memory resources based on their configuration.

What you see:

  • Ranking from 🥇 (highest) to 5️⃣ (fifth highest)
  • Pod name and namespace
    • -
  • Resource usage in CPU cores and memory GiB
    • +
  • Resource requests - what each pod is asking for (not actual usage)
  • QoS class (Guaranteed, Burstable, BestEffort)
+

Important distinction:

+
    +
  • Requests ≠ Usage - This shows what pods are configured to request, not what they actually use
    • +
  • Configuration-based - Based on pod specifications, not real-time metrics
    • +
  • Planning tool - Helps understand resource allocation planning
    • +
+

Why it matters:

-

Identifying top consumers helps you understand which applications are using the most resources and may need optimization.

+

Shows which workloads are configured to use the most resources, helping with capacity planning and optimization.

` }, @@ -3153,8 +3167,8 @@
-
CPU: ${formatCpuValue(consumer.cpu_requests)}
-
Memory: ${formatMemoryValue(consumer.memory_requests)}
+
CPU Request: ${formatCpuValue(consumer.cpu_requests)}
+
Memory Request: ${formatMemoryValue(consumer.memory_requests)}
${consumer.qos_class}
`;