How can you optimize Kubernetes monitoring using the Cluster Agent's Cluster Checks?

Identify checks that are redundant when run per-node - typically checks against an external endpoint, a load-balanced Kubernetes Service, or a managed external database - since running the same check independently on every node Agent wastes resources checking the exact same target repeatedly with no added value.

Configure those specific checks as Cluster Checks so the Cluster Agent dispatches each one to run exactly once across the cluster, rather than once per node, which both reduces redundant load on the checked target and lowers overall Agent resource consumption cluster-wide.

For clusters where check volume itself is high enough to strain the node Agents dispatched to run them, deploy dedicated Cluster Check Runners - a small, separate pool of Agents whose only job is running cluster checks - so that regular per-node endpoint checks aren't competing for the same Agent resources as cluster-wide checks.

Keep genuinely node-local checks (like a container runtime check, or a check on a service that's only meaningfully checked from the node it lives on) as regular per-node Autodiscovery checks rather than Cluster Checks - converting truly node-specific checks to cluster-wide ones would actually lose the node-specific context that made them useful in the first place.