Merge pull request #2540 from splunk/repo-sync

Pulling refs/heads/main into main

Author: jcatera-splunk

admin/authentication/allow-services.rst

@@ -28,7 +28,7 @@ Ensure that you give the proxy the ability to resolve the network names and make
 Use the Splunk Distribution of the OpenTelemetry Collector
 =======================================================================
 
-Use the :new-page:`Splunk Distribution of OpenTelemetry Collector <https://docs.splunk.com/Observability/gdi/opentelemetry/deployment-modes.html>` in data forwarding (gateway) mode. You can forward metrics locally to the Splunk Distribution of OpenTelemetry Collector, which serves as your local store-and-forward service for telemetry.
+The :new-page:`Splunk Distribution of OpenTelemetry Collector <https://docs.splunk.com/Observability/gdi/opentelemetry/deployment-modes.html>` supports proxies. You can configure proxies on each collector, or more typically, you would configure a collector in data forwarding (gateway) mode. In the gateway mode, you only need to configure the gateway collector(s) with the proxy settings; all other collectors can simply send data to the gateway collector.
 
 Ensure that you give the Splunk Distribution of OpenTelemetry Collector the ability to resolve the network names and make outbound HTTPS network connections to the URLs listed in :ref:`allow-urls` or the domains listed in :ref:`allow-domains`. Verify also the list of :ref:`exposed ports and endpoints <otel-exposed-endpoints>`.
 

data-visualization/charts/export-and-share-charts.rst

@@ -16,7 +16,7 @@ Export chart contents
 
 For line charts, area charts, and column charts, you can export the chart contents to a CSV file. The most recent 100 data points will be exported, along with the values of the dimensions associated with them.
 
-To export a chart, select :strong:`Export Chart as CSV` from the chart's :guilabel:`Actions` menu (|more|).
+To export a chart, first select :strong:`Data table` tab, next select :strong:`Export as CSV` download icon in the table headers row on the last column (the right side corner).
 
 .. note:: List charts and table charts can't be exported because they don't have a data table.
 

gdi/get-data-in/connect/aws/aws-connect-polling.rst

@@ -113,7 +113,7 @@ Use the check box options in the guided setup to limit the scope of your data co
 * Select which :ref:`AWS regions <aws-regions>` to fetch data from.
 * Select which AWS services to fetch data from.
 
-.. note:: You can also chose to import recommended stats. Learn more at :ref:`aws-recommended-stats`.
+.. note:: You can also choose to import recommended stats. Learn more at :ref:`aws-recommended-stats`.
 
 To limit data collection, you can also:
 
@@ -136,4 +136,4 @@ Next steps
 After you connect Splunk Observability Cloud with AWS, you can use Splunk Observability Cloud to track a series of metrics and analyze your AWS data in real time. 
 
 - See the AWS official documentation for a list of the available AWS resources.
-- See :ref:`how to leverage data from integration with AWS <aws-post-install>` for more information.
+- See :ref:`how to leverage data from integration with AWS <aws-post-install>` for more information.

gdi/get-data-in/rum/browser/manual-rum-browser-instrumentation.rst

@@ -49,6 +49,8 @@ The following example shows how to set the user ID globally:
 
 .. code-block:: javascript
 
+   import SplunkRum from '@splunk/otel-web';
+
    SplunkRum.setGlobalAttributes({
       'enduser.id': 'Test User'
    });

gdi/opentelemetry/automatic-discovery/k8s/k8s-advanced-config.rst

@@ -37,6 +37,8 @@ By default, the Splunk Distribution of OpenTelemetry Collector uses the latest v
         environment: prd
         certmanager:
           enabled: true
+        operatorcrds:
+          install: true
         operator:
           enabled: true
         instrumentation:
@@ -78,6 +80,8 @@ Follow these steps to activate Profiling for a language:
 
     .. code-block:: yaml
 
+        operatorcrds:
+          install: true
         operator:
           enabled: true
         instrumentation:  
@@ -112,6 +116,8 @@ Follow these steps to activate runtime metrics collection:
 
     .. code-block:: yaml
 
+      operatorcrds:
+        install: true
       operator:
         enabled: true
       instrumentation:  
@@ -126,6 +132,8 @@ Follow these steps to activate runtime metrics collection:
 
     .. code-block:: yaml
 
+      operatorcrds:
+        install: true
       operator:
         enabled: true
       instrumentation:
@@ -169,6 +177,8 @@ Follow these steps to send data to a gateway endpoint:
         environment: prd
         certmanager:
           enabled: true
+        operatorcrds:
+          install: true
         operator:
           enabled: true
         instrumentation:
@@ -194,6 +204,8 @@ You can also automatically send data to a deployed gateway endpoint by setting `
     environment: prd
     certmanager:
       enabled: true
+    operatorcrds:
+      install: true
     operator:
       enabled: true
                 

gdi/opentelemetry/automatic-discovery/k8s/k8s-backend.rst

@@ -79,6 +79,8 @@ Populate values.yaml with the following fields and values:
     accessToken: <splunk_access_token>
   
   # Activates the OpenTelemetry Kubernetes Operator
+  operatorcrds:
+    install: true
   operator:
     enabled: true
 
@@ -113,6 +115,8 @@ The following example YAML includes ``certmanager.enabled=true`` and ``operatorc
   
   certmanager:
     enabled: true
+  operatorcrds:
+    install: true
   operator:
     enabled: true
   operatorcrds:
@@ -165,6 +169,8 @@ The following examples show how to set the attribute using each method:
           
           certmanager:
             enabled: true
+          operatorcrds:
+            install: true
           operator:
             enabled: true
 
@@ -174,6 +180,8 @@ The following examples show how to set the attribute using each method:
 
       .. code-block:: yaml
 
+          operatorcrds:
+            install: true
           operator:
             enabled: true
           instrumentation:

gdi/opentelemetry/automatic-discovery/k8s/k8s-java-traces-tutorial/config-k8s-for-java.rst

@@ -56,6 +56,9 @@ Now, you need to configure Helm to correctly install the Splunk Distribution of
         * - ``certmanager.enabled``
           - ``true``
           - Activates the certification manager for Helm
+        * - ``operatorcrds.install``
+          - ``true``
+          - Installs the CRDs used by the OpenTelemetry Kubernetes Operator
         * - ``operator.enabled``
           - ``true``
           - Activates the OpenTelemetry Kubernetes Operator
@@ -75,6 +78,8 @@ Now, you need to configure Helm to correctly install the Splunk Distribution of
         environment: prd
         certmanager:
           enabled: true
+        operatorcrds:
+          install: true
         operator:
           enabled: true
 

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

@@ -250,6 +250,8 @@ For the Operator:
 
 .. code-block:: yaml
 
+  operatorcrds:
+    install: true
   operator:
     enabled: true