Added a note that cgroup metrics exposed by cAdvisor cannot be collected by the Splunk OTel collector.

Author: jcatera-splunk

gdi/monitors-monitoring/cadvisor.rst

@@ -16,8 +16,11 @@ If you are using Kubernetes, consider the
 expose cAdvisor on a network port, even though they are running it
 within Kubelet.
 
+.. :note:: The Splunk Distribution of OpenTelemetry Collector cannot collect specific cgroup metrics exposed by cAdvisor, such as ``container_cpu_cfs_*`` 
+   in managed environments such as Amazon EKS, and the supported `kubeletstats` receiver does not expose these metrics by default.
+
 If you are running containers with Docker, retrieved metrics might
-overlap with ``docker-container-stats``\ '. Consider not enabling the
+overlap with ``docker-container-stats``. Consider not enabling the
 Docker monitor in a Kubernetes environment, or else use filtering to
 allow only certain metrics. This will cause the built-in Docker
 dashboards to be blank, but container metrics will be available on the