Documentation for automated readers
A curated documentation index is available at: https://grafana.com/llms.txt
A complete documentation index is available at: https://grafana.com/llms-full.txt
These indexes can help with page discovery before fetching individual documents.
This page is also available in Markdown, which may be easier for automated readers and AI tools to parse than HTML. The Markdown version is available at https://grafana.com/docs/grafana-cloud/machine-learning/sift/analyses/resource-contentions.md, or by sending Accept: text/markdown to https://grafana.com/docs/grafana-cloud/machine-learning/sift/analyses/resource-contentions/. For broader documentation discovery, the curated index is available at https://grafana.com/llms.txt and the complete index is available at https://grafana.com/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


