Updated the cAdvisor doc based on feedback from engineering.

Author: jcatera-splunk

gdi/monitors-monitoring/cadvisor.rst

@@ -9,16 +9,28 @@ cAdvisor
 The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the
 cAdvisor monitor type to pull metrics directly from cAdvisor. By
 default, it runs on port 4193, but it can be configured to any other
-port.
+port. 
+
+This integration is available on Kubernetes, Linux, and Windows.
+
+cAdvisor with Kubernetes
+------------------------
 
 If you are using Kubernetes, consider the
 :ref:`kubelet-stats-receiver` because many Kubernetes nodes do not
 expose cAdvisor on a network port, even though they are running it
 within Kubelet.
 
-.. note:: The Splunk Distribution of OpenTelemetry Collector has limitations in managed environments such as Amazon EKS. 
-   For example, the collector cannot collect specific cgroup metrics exposed by cAdvisor, such as ``container_cpu_cfs_*``. 
-   The ``kubeletstats`` receiver also does not expose these metrics by default. 
+If you are using Kubernetes, consider the Kubelet stats receiver 
+because many Kubernetes nodes do not expose cAdvisor on a network port, 
+even though they are running it within Kubelet. Because the Splunk Distribution 
+of OpenTelemetry Collector has limitations in managed environments such as Amazon EKS, 
+you can use a :ref:`Prometheus receiver <prometheus_receiver>` to collect specific 
+cgroup metrics exposed by cAdvisor, such as ``container_cpu_cfs_*``. 
+The kubeletstats receiver also does not expose these metrics by default.
+
+cAdvisor with Docker
+---------------------
 
 If you are running containers with Docker, retrieved metrics might
 overlap with ``docker-container-stats``. Consider not enabling the
@@ -27,13 +39,10 @@ allow only certain metrics. This will cause the built-in Docker
 dashboards to be blank, but container metrics will be available on the
 Kubernetes dashboards instead.
 
-This integration is available on Kubernetes, Linux, and Windows.
 
 Benefits
 --------
 
-
-
 .. raw:: html
 
    <div class="include-start" id="benefits.rst"></div>
@@ -45,13 +54,9 @@ Benefits
    <div class="include-stop" id="benefits.rst"></div>
 
 
-
-
 Installation
 ------------
 
-
-
 .. raw:: html
 
    <div class="include-start" id="collector-installation-linux.rst"></div>
@@ -63,13 +68,9 @@ Installation
    <div class="include-stop" id="collector-installation-linux.rst"></div>
 
 
-
-
 Configuration
 -------------
 
-
-
 .. raw:: html
 
    <div class="include-start" id="configuration.rst"></div>
@@ -81,10 +82,11 @@ Configuration
    <div class="include-stop" id="configuration.rst"></div>
 
 
+Examples
+^^^^^^^^
 
-
-Example
-~~~~~~~
+Activate integration
+####################
 
 To activate this integration, add the following to your Collector
 configuration:
@@ -106,8 +108,55 @@ section of your configuration file:
        metrics:
          receivers: [smartagent/cadvisor]
 
+.. _prometheus_receiver:
+
+Prometheus receiver
+###################
+
+.. code:: yaml
+
+   receivers:
+     prometheus/cadvisor:
+       config:
+         scrape_configs:
+           - job_name: 'kubernetes-nodes-cadvisor'
+             scheme: https
+             bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
+             kubernetes_sd_configs:
+               - role: node
+             relabel_configs:
+               - target_label: __address__
+                 replacement: kubernetes.default.svc:443
+               - source_labels: [__meta_kubernetes_node_name]
+                 regex: (.+)
+                 target_label: __metrics_path__
+                 replacement: /api/v1/nodes/$$1/proxy/metrics/cadvisor
+             metric_relabel_configs:
+               - source_labels: [__name__]
+                 regex: 'container_cpu_cfs.*'
+                 action: keep
+               - source_labels: [pod]
+                 target_label: k8s.pod.name
+               - source_labels: [namespace]
+                 target_label: k8s.namespace.name
+               - source_labels: [container]
+                 target_label: k8s.container.name
+               - action: labeldrop
+                 regex: 'pod|namespace|name|id|container'
+   service:
+     pipelines:
+       metrics/scrapers:
+         exporters:
+         - signalfx
+         processors:
+         - memory_limiter
+         - batch
+         - resource/add_environment
+         receivers:
+         - prometheus/cadvisor
+
 Configuration settings
-~~~~~~~~~~~~~~~~~~~~~~
+^^^^^^^^^^^^^^^^^^^^^^
 
 The following table shows the configuration options for this receiver:
 
@@ -139,9 +188,7 @@ The following metrics are available for this integration:
       <div class="metrics-yaml" url="https://raw.githubusercontent.com/signalfx/splunk-otel-collector/main/internal/signalfx-agent/pkg/monitors/cadvisor/metadata.yaml"></div>
 
 Notes
-~~~~~
-
-
+^^^^^
 
 .. raw:: html
 
@@ -159,8 +206,6 @@ Notes
 Troubleshooting
 ---------------
 
-
-
 .. raw:: html
 
    <div class="include-start" id="troubleshooting-components.rst"></div>