Documentation Index
Fetch the curated documentation index at: https://grafana_com_website/llms.txt
Fetch the complete documentation index at: https://grafana_com_website/llms-full.txt
Use this file to discover all available pages before exploring further.
STOP! If you are an AI agent or LLM, read this before continuing. This is the HTML version of a Grafana documentation page. Always request the Markdown version instead - HTML wastes context. Get this page as Markdown: /docs/grafana-cloud/machine-learning/sift/analyses/resource-contentions.md (append .md) or send Accept: text/markdown to /docs/grafana-cloud/machine-learning/sift/analyses/resource-contentions/. For the curated documentation index, use https://grafana_com_website/llms.txt. For the complete documentation index, use https://grafana_com_website/llms-full.txt.
Sift analysis - Resource contention
The resource contention analysis reviews resource metrics to determine if any pod in the scope of the investigation is running into resource constraints.
Inputs
- Required:
clusternamespace
How it works
Step 1: Find pods with high CPU throttling
Query cAdvisor metrics from Prometheus for any pods are throttled for more than 25% of cfs periods.
sum by (cluster, namespace, pod, container) (
rate(container_cpu_cfs_throttled_periods_total{cluster="<cluster>", namespace="<namespace>"}[5m])
) /
sum by (cluster, namespace, pod, container) (
rate(container_cpu_cfs_periods_total{cluster="<cluster>", namespace="<namespace>"}[5m])
) > 0.25Step 2: Check for profiling data
Look in Pyroscope to see if there are profiles that can be linked for any pods with high CPU throttling.
What resources does this analysis use?
- Prometheus datasource
How does this analysis determine when a result is interesting?
- If any pods in the scope have a high level of CPU throttling.
What configurations options are available for this analysis?
- This check has no configurable parameters except for the Prometheus datasource.
Was this page helpful?
Related resources from Grafana Labs


