diff --git a/app/static/index.html b/app/static/index.html
index 2d793b3..554b227 100644
--- a/app/static/index.html
+++ b/app/static/index.html
@@ -1385,20 +1385,20 @@
- Pods ❓:
- -
+ CPU Overcommit ❓:
+ -
- Namespaces ❓:
- -
+ Memory Overcommit ❓:
+ -
- Critical Issues ❓:
- -
+ Namespaces in Overcommit ❓:
+ -
- Overcommit ❓:
- -
+ Resource Quota Coverage ❓:
+ -
@@ -2903,6 +2903,94 @@
Non-critical applications, batch jobs, or development workloads where performance isn't critical.
`
+ },
+ 'cpu-overcommit': {
+ title: 'CPU Overcommit - Resource Allocation',
+ content: `
+
+
CPU Overcommit shows how much CPU is requested compared to available capacity.
+
+
What this means:
+
+ - 0-100% - Normal allocation (requests ≤ capacity)
+ - 100-150% - Moderate overcommit (some risk)
+ - 150%+ - High overcommit (high risk)
+
+
+
Why overcommit happens:
+
+ - Applications don't always use their full CPU allocation
+ - Allows more workloads to run on limited hardware
+ - Kubernetes can schedule more pods than physical cores
+
+
+ `
+ },
+ 'memory-overcommit': {
+ title: 'Memory Overcommit - Memory Allocation',
+ content: `
+
+
Memory Overcommit shows how much memory is requested compared to available capacity.
+
+
What this means:
+
+ - 0-100% - Normal allocation (requests ≤ capacity)
+ - 100-150% - Moderate overcommit (some risk)
+ - 150%+ - High overcommit (high risk)
+
+
+
Memory vs CPU:
+
+ - Memory overcommit is more dangerous than CPU overcommit
+ - Memory cannot be "borrowed" like CPU cycles
+ - High memory overcommit can cause OOM (Out of Memory) kills
+
+
+ `
+ },
+ 'namespaces-overcommit': {
+ title: 'Namespaces in Overcommit',
+ content: `
+
+
Namespaces in Overcommit shows how many namespaces have resource limits exceeding their requests.
+
+
What this means:
+
+ - Each namespace can have resource quotas
+ - When limits > requests, overcommit occurs
+ - This metric counts affected namespaces
+
+
+
Why monitor this:
+
+ - Identifies which namespaces need attention
+ - Helps prioritize resource optimization
+ - Prevents resource starvation across namespaces
+
+
+ `
+ },
+ 'quota-coverage': {
+ title: 'Resource Quota Coverage',
+ content: `
+
+
Resource Quota Coverage shows what percentage of namespaces have resource quotas defined.
+
+
What this means:
+
+ - 80-100% - Excellent coverage
+ - 50-80% - Good coverage
+ - 0-50% - Poor coverage
+
+
+
Why quotas matter:
+
+ - Prevent one namespace from consuming all resources
+ - Ensure fair resource distribution
+ - Provide resource isolation and limits
+
+
+ `
}
};
@@ -2971,11 +3059,17 @@
healthSubtitle.textContent = 'All systems operational';
}
- // Update metrics
+ // Update basic metrics (cards superiores)
document.getElementById('totalPods').textContent = healthData.total_pods;
document.getElementById('totalNamespaces').textContent = healthData.total_namespaces;
document.getElementById('criticalIssues').textContent = healthData.critical_issues;
+ // Update health section metrics (métricas específicas de saúde)
+ document.getElementById('cpuOvercommitStatus').textContent = `${healthData.cpu_overcommit_percentage.toFixed(1)}%`;
+ document.getElementById('memoryOvercommitStatus').textContent = `${healthData.memory_overcommit_percentage.toFixed(1)}%`;
+ document.getElementById('namespacesInOvercommit').textContent = healthData.namespaces_in_overcommit;
+ document.getElementById('quotaCoverage').textContent = `${(healthData.resource_quota_coverage * 100).toFixed(0)}%`;
+
// Update overcommit status
const cpuOvercommit = healthData.cpu_overcommit_percentage;
const memoryOvercommit = healthData.memory_overcommit_percentage;