Pulling refs/heads/main into main

gdi/opentelemetry/collector-kubernetes/install-k8s.rst

@@ -72,7 +72,7 @@ Depending on your destination, you need:
    * ``splunkObservability.accessToken``. Your Splunk Observability Cloud org access token with ingest authorization scope. See :ref:`admin-org-tokens`.
    * ``splunkObservability.realm``. Splunk realm to send telemetry data to. The default is ``us0``. See :new-page:`realms <https://dev.splunk.com/observability/docs/realms_in_endpoints/>`.
 
-.. note:: The Collector for Kubernetes uses ``main`` as the default Splunk platform index.
+.. note:: The Collector for Kubernetes uses ``main`` as the default Splunk platform index. You can use annotations to send data to different indexes. See :ref:`kubernetes-config-logs-annotations-indexes` for more information. 
 
 Deploy the Helm chart
 ==============================================

gdi/opentelemetry/collector-kubernetes/kubernetes-config-logs.rst

@@ -8,7 +8,6 @@ Collect logs and events for the Collector for Kubernetes
 .. meta::
       :description: Configure logs and events for the Splunk Distribution of OpenTelemetry Collector for Kubernetes.
 
-
 .. note:: See how to configure the Collector for Kubernetes at :ref:`otel-kubernetes-config` and :ref:`otel-kubernetes-config-advanced`.
 
 Starting on version 0.86.0, the Splunk Distribution of the Collector for Kubernetes collects native OpenTelemetry logs by default.
@@ -77,17 +76,26 @@ To process multi-line logs, add the following section to your values.yaml config
 
 Use :new-page:`regex101 <https://regex101.com/ >` to find a Golang regex that works for your format and specify it in the config file for the config option ``firstEntryRegex``.
 
+.. _kubernetes-config-logs-annotations:
+
 Manage log ingestion using annotations
 ===========================================================================
 
-Use the ``splunk.com/index`` annotation on pods or namespaces to indicate which Splunk platform indexes you want to send logs to. Pod annotation will take precedence over namespace annotation when both are annotated. 
+.. _kubernetes-config-logs-annotations-indexes:
+
+Send logs to different indexes
+-----------------------------------------------------
+
+The Collector for Kubernetes uses ``main`` as the default Splunk platform index. Use the ``splunk.com/index`` annotation on pods or namespaces to indicate which Splunk platform indexes you want to send logs to. 
 
 For example, to send logs from the ``kube-system`` namespace to the ``k8s_events`` index, use the command: 
 
 .. code-block:: bash
 
     kubectl annotate namespace kube-system splunk.com/index=k8s_events
 
+.. note:: A pod annotation takes precedence over a namespace annotation when both are annotated.     
+
 Filter logs using pod or namespace annotations
 -----------------------------------------------------
 

logs/processors.rst

@@ -41,6 +41,9 @@ Going forward after the transition to Log Observer Connect, you can process data
    * - Data Stream Processor
      - See :new-page:`Use the Data Stream Processor <https://docs.splunk.com/Documentation/DSP/1.4.2/User/About>`.
 
+   * - Ingest Processor
+     - See :new-page:`About Ingest Processor <https://docs.splunk.com/Documentation/SplunkCloud/latest/IngestProcessor/AboutIngestProcessorSolution>`.  
+
 
 Prepackaged processing rules
 =============================================================================