Merge pull request #1747 from splunk/repo-sync

Pulling refs/heads/main into main

Author: jcatera-splunk

_images/gdi/AWS_PL_region1.jpg

@@ -12,6 +12,9 @@
    * - :ref:`apache-spark-receiver` (``apachespark``) 
      - Fetches metrics for an Apache Spark cluster through the Apache Spark REST API. 
      - Metrics
+   * - :ref:`activedirectory-ds-receiver` (``active_directory_ds``)
+     - Metrics
+     - Scrapes metrics relating to an Active Directory domain controller using the Windows Performance Counters.
    * - :ref:`awsecscontainermetrics-receiver` (``awsecscontainermetrics``) 
      - Reads task metadata and docker stats from Amazon ECS and generates resource usage metrics.
      - Metrics

_images/gdi/AWS_PL_region1.png

@@ -1,6 +1,6 @@
 Splunk RUM for Mobile supports the following versions:
 
 * iOS 15 and higher
-* iPadOS 13 and higher
+* iPadOS 15 and higher
 
 Splunk RUM supports Apple Silicon.

_images/gdi/AWS_PL_region2.png

@@ -53,7 +53,7 @@ The following settings are specific to the Splunk Distribution of OpenTelemetry
    * - ``SPLUNK_ACCESS_TOKEN``
      - A Splunk authentication token that lets exporters send data directly to Splunk Observability Cloud. Unset by default. Not required unless you need to send data to the Splunk Observability Cloud ingest endpoint. See :ref:`admin-tokens`.
    * - ``SPLUNK_REALM``
-     - The name of your organization's realm, for example, ``us0``. When you set the realm, telemetry is sent directly to the ingest endpoint of Splunk Observability Cloud, bypassing the Splunk Distribution of OpenTelemetry Collector.
+     - The name of your organization's realm, for example, ``us0``. When you set the realm, telemetry is sent directly to the ingest endpoint of Splunk Observability Cloud, bypassing the Splunk Distribution of OpenTelemetry Collector. This setting applies only to metrics and traces and does not work for logs.
    * - ``SPLUNK_TRACE_RESPONSE_HEADER_ENABLED``
      - Lets you add server trace information to HTTP response headers using the ``net/http`` instrumentation package. For more information, see :ref:`server-trace-information-go`. The default value is ``true``.
    * - ``OTEL_LOG_LEVEL``
@@ -104,6 +104,8 @@ The following settings control trace exporters and their endpoints:
      - The traces exporter to use. The default value is ``otlp``. Acceptable values are ``otlp`` and ``none``. Setting ``none`` deactivates trace exports.
    * - ``OTEL_METRICS_EXPORTER``
      - The metrics exporter to use. The default value is ``otlp``. Accepted values are ``otlp`` and ``none``. Setting ``none`` deactivates metric exports.
+   * - ``OTEL_LOGS_EXPORTER``
+     - The logs exporter to use. The default value is ``none``. Accepted values are ``otlp`` and ``none``. Setting ``none`` deactivates logs exports.
    * - ``OTEL_METRIC_EXPORT_INTERVAL``
      - Interval, in milliseconds, between the start of two export attempts. The default value is ``60000``.
    * - ``OTEL_METRIC_EXPORT_TIMEOUT``
@@ -114,7 +116,9 @@ The following settings control trace exporters and their endpoints:
      - The OTLP endpoint for traces. The default value is ``http://localhost:4317``.
    * - ``OTEL_EXPORTER_OTLP_METRICS_ENDPOINT``
      - The OTLP endpoint. The default value is ``http://localhost:4317``.
-
+   * - ``OTEL_EXPORTER_OTLP_LOGS_ENDPOINT``
+     - The OTLP endpoint. The default value is ``http://localhost:4317``.
+     
 To send data directly to Splunk Observability Cloud, see :ref:`export-directly-to-olly-cloud-go`.
 
 .. _trace-sampling-settings-go-otel:

_images/gdi/AWS_PL_region3.png

@@ -169,7 +169,9 @@ The following example shows how to update a deployment to expose environment var
 Send data directly to Splunk Observability Cloud
 ==================================================================
 
-By default, all telemetry is sent to the local instance of the Splunk Distribution of OpenTelemetry Collector.
+By default, all telemetry is sent to the local OpenTelemetry Collector before being forwarded to Splunk Observability Cloud.
+It is also possible to send data directly to Splunk Observability Cloud without using the OpenTelemetry Collector.
+.. note:: Sending data directly to Splunk Observability Cloud is supported only for traces and metrics. Logs cannot be sent using this method.
 
 If you need to send data directly to Splunk Observability Cloud, set the following environment variables:
 

_images/logs/CreateUser.png

@@ -419,19 +419,19 @@ To deploy the .NET zero-code instrumentation in Kubernetes, follow these steps:
 
    .. code-block:: shell
 
-   splunk-launch.sh dotnet <application>.
+      splunk-launch.sh dotnet <application>.
 
    **For Windows:**
 
    .. code-block:: powershell
 
-   splunk-launch.cmd dotnet <application>.   
+      splunk-launch.cmd dotnet <application>.   
 
    Example:
 
    .. code-block:: docker
 
-   ENTRYPOINT ["./splunk-launch.sh", "dotnet", "myapp.dll"]
+      ENTRYPOINT ["./splunk-launch.sh", "dotnet", "myapp.dll"]
 
 #. Configure the Kubernetes Downward API to expose environment variables to Kubernetes resources. The following example demonstrates how to update a deployment to expose environment variables by adding the agent configuration under the ``.spec.template.spec.containers.env`` section: