Merge pull request #2032 from splunk/urbiz-DG25571-kbs-ootb-metrics

[DG25571]: Adding extra OOTB Collector metrics

Author: aurbiztondo-splunk

gdi/opentelemetry/collector-kubernetes/metrics-ootb-k8s.rst

@@ -19,9 +19,11 @@ Learn more about the Collector's configuration and data processing at:
 * :ref:`otel-data-processing`
 * :ref:`signalfx-exporter`
 
-.. note:: In addition to the metrics shown on this page, most instances also send metrics from the :ref:`kubernetes-cluster-receiver`. Cluster Receiver metrics are an important part of monitoring any kubernets installation. Refer to that page as well as the metrics listed here.
-          
-To see the Collector's internal metrics, refer to :ref:`metrics-internal-collector`.
+.. note:: 
+
+  In addition to the metrics shown on this page, most Collector instances also send metrics from the :ref:`kubernetes-cluster-receiver`, which are an important part of monitoring any Kubernetes installation. Refer to that page as well as the metrics listed here. 
+  
+  For the Collector's internal metrics, see :ref:`metrics-internal-collector`.
 
 Container level metrics and dimensions
 ============================================================================
@@ -121,6 +123,18 @@ Container level metrics and dimensions
     - No
     - Yes
 
+  * - ``k8s.container.ephemeralstorage_limit``
+    - Container ``ephemeralstorage_limit``
+    - :ref:`ootb-metrics-k8s-attributes`
+    - No
+    - No
+
+  * - ``k8s.container.ephemeralstorage_request``
+    - Container ``ephemeralstorage_request``
+    - :ref:`ootb-metrics-k8s-attributes`
+    - No
+    - No
+
   * - ``k8s.container.memory_limit``
     - Container ``memory_limit``
     - :ref:`ootb-metrics-k8s-attributes`
@@ -133,6 +147,24 @@ Container level metrics and dimensions
     - No
     - Yes
 
+  * - ``k8s.container.restarts``
+    - Container ``restarts``
+    - :ref:`ootb-metrics-k8s-attributes`
+    - No
+    - Yes
+
+  * - ``k8s.container.storage_limit``
+    - Container ``storage_limit``
+    - :ref:`ootb-metrics-k8s-attributes`
+    - No
+    - No
+
+  * - ``k8s.container.storage_request``
+    - Container ``storage_requests``
+    - :ref:`ootb-metrics-k8s-attributes`
+    - No
+    - No
+
 Pod level metrics and dimensions
 ============================================================================
 
@@ -219,6 +251,11 @@ Pod level metrics and dimensions
       * :ref:`ootb-metrics-k8s-attributes`
     - Yes
 
+  * - ``k8s.pod.status_reason``
+    - Information on the pod status
+    - 
+    - Yes
+
 Node level metrics and dimensions
 ============================================================================
 
@@ -238,6 +275,11 @@ Node level metrics and dimensions
     - Attributes
     - Exported?
 
+  * - ``k8s.node.condition``
+    - Node condition
+    - 
+    - No
+
   * - ``k8s.node.cpu.time``
     - Node CPU time
     - 
@@ -524,6 +566,115 @@ The following distributions support control plane metrics configuration:
 
 For information about control plane metrics, see :ref:`otel-kubernetes-config-advanced-control-plane`.
 
+.. _ootb-metrics-k8s-other:
+
+Other metrics
+============================================================================
+
+.. caution:: 
+  
+  The :strong:`Exported?` column indicates if the metric is finally sent to Splunk Observability Cloud after going through the Collector pipelines. 
+
+Other available metrics include:
+
+.. list-table::
+  :widths: 75 25
+  :width: 100%
+  :header-rows: 1
+
+  * - Metric name
+    - Exported?
+
+  * - ``k8s.deployment.desired``
+    - Yes
+
+  * - ``k8s.deployment.available``
+    - Yes
+
+  * - ``k8s.daemonset.current_scheduled_nodes``
+    - Yes
+
+  * - ``k8s.daemonset.current_scheduled_nodes`` 
+    - Yes
+
+  * - ``k8s.daemonset.misscheduled_nodes`` 
+    - Yes
+
+  * - ``k8s.daemonset.ready_nodes``
+    - Yes
+
+  * - ``k8s.hpa.max_replicas``
+    - No
+
+  * - ``k8s.hpa.min_replicas``
+    - No
+
+  * - ``k8s.hpa.current_replicas``
+    - No
+
+  * - ``k8s.hpa.desired_replicas``
+    - No
+
+  * - ``k8s.job.active_pods``
+    - No
+
+  * - ``k8s.job.desired_successful_pods``
+    - No
+
+  * - ``k8s.job.failed_pods``
+    - No
+
+  * - ``k8s.job.max_parallel_pods``
+    - No
+
+  * - ``k8s.job.successful_pods``
+    - No
+
+  * - ``k8s.namespace.phase``
+    - Yes
+
+  * - ``k8s.replicaset.desired``
+    - Yes
+
+  * - ``k8s.replicaset.available``
+    - Yes
+
+  * - ``k8s.replication_controller.desired``
+    - Yes
+
+  * - ``k8s.replication_controller.available``
+    - Yes
+
+  * - ``k8s.resource_quota.hard_limit``
+    - Yes
+
+  * - ``k8s.resource_quota.used``
+    - Yes
+
+  * - ``k8s.statefulset.desired_pods``
+    - No
+
+  * - ``k8s.statefulset.ready_pods``
+    - No
+
+  * - ``k8s.statefulset.current_pods``
+    - No
+
+  * - ``k8s.statefulset.updated_pods``
+    - No
+
+  * - ``openshift.clusterquota.limit``
+    - Yes
+
+  * - ``openshift.clusterquota.used``
+    - Yes
+
+  * - ``openshift.appliedclusterquota.limit``
+    - Yes
+
+  * - ``openshift.appliedclusterquota.used``
+    - Yes
+
 .. _ootb-metrics-k8s-attributes:
 
 Standard resource dimensions

gdi/opentelemetry/components/kubernetes-cluster-receiver.rst

@@ -16,7 +16,7 @@ Kubernetes version 1.21 and higher is compatible with the Kubernetes navigator.
 Get started
 ======================
 
-By default, the Kubernetes cluster receiver is already activated in the Helm chart of the Splunk OpenTelemetry Collectors. See :ref:`otel-kubernetes-config` for more information.
+By default, the Kubernetes cluster receiver is already activated in the Helm chart of the Splunk OpenTelemetry Collectors. See :ref:`otel-kubernetes-config` for more information, including the default :ref:`ootb-metrics-k8s`.
 
 To activate the Kubernetes cluster receiver manually in the Collector configuration, add ``k8s_cluster`` to the ``receivers`` section of your configuration file, as shown in the following example: