A water-utility OKE cluster shows citizen-portal pods stuck Pending while nodes report not Ready. Which Monitoring approach matches what OCI emits automatically for the cluster and nodes?
Select an answer to reveal the explanation.
Short Explanation
oci_oke is the cluster’s built-in dashboard for control plane and nodes—scheduling stuck pods and Ready pressure live there. Your app’s own RED numbers are custom metrics or APM, not those OKE figures.
Full Explanation
Oracle Kubernetes Engine emits metrics in the oci_oke namespace automatically for clusters you create. Useful developer signals include API server request/response counts, unschedulable pods, node state, and Kubernetes node conditions such as Ready, memory/disk/PID pressure, and network. Application-level RED metrics for your process are custom metrics or APM, not these control-plane and node figures. oci_faas and API Gateway metrics answer different service questions.