Merge pull request #2349 from splunk/repo-sync

Pulling refs/heads/main into main

Author: pauljwil

gdi/get-data-in/rum/browser/install-rum-browser.rst

@@ -226,7 +226,7 @@ Opt out of error.message collection
 To avoid collecting ``error.message`` responses, deactivate the errors instrumentation as in the following example:
 
 .. code-block:: html
-   :emphasize-lines: 7
+   :emphasize-lines: 8
 
    <script src="https://cdn.signalfx.com/o11y-gdi-rum/latest/splunk-otel-web.js" crossorigin="anonymous"></script>
    <script>

gdi/get-data-in/serverless/aws/otel-lambda-layer/instrumentation/dotnet-lambdas.rst

@@ -14,7 +14,7 @@ You can instrument a .NET AWS Lambda function to send traces to Splunk Observabi
 * :new-page:`OpenTelemetry.Instrumentation.AWS <https://www.nuget.org/packages/OpenTelemetry.Instrumentation.AWS>`
 * :new-page:`OpenTelemetry.Instrumentation.AWSLambda <https://www.nuget.org/packages/OpenTelemetry.Instrumentation.AWSLambda>`
 * :new-page:`OpenTelemetry.Instrumentation.Http <https://www.nuget.org/packages/OpenTelemetry.Instrumentation.Http>`
-* :new-page:`OpenTelemetry.ResourceDetectors.AWS <https://www.nuget.org/packages/OpenTelemetry.ResourceDetectors.AWS>`
+* :new-page:`OpenTelemetry.Resources.AWS <https://www.nuget.org/packages/OpenTelemetry.Resources.AWS/>`
 
 To instrument a .NET function in AWS Lambda for Splunk APM, follow these steps:
 
@@ -26,7 +26,6 @@ To instrument a .NET function in AWS Lambda for Splunk APM, follow these steps:
    using OpenTelemetry;
    using OpenTelemetry.Exporter;
    using OpenTelemetry.Instrumentation.AWSLambda;
-   using OpenTelemetry.ResourceDetectors.AWS;
    using OpenTelemetry.Resources;
    using OpenTelemetry.Trace;
    using System.Diagnostics;
@@ -72,8 +71,8 @@ To instrument a .NET function in AWS Lambda for Splunk APM, follow these steps:
                .ConfigureResource(configure => configure
                      .AddService(serviceName, serviceVersion: "1.0.0")
                      // Different resource detectors can be found at
-                     // https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.ResourceDetectors.AWS#usage
-                     .AddDetector(new AWSEBSResourceDetector()))
+                     // https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Resources.AWS#usage
+                     .AddAWSEBSDetector())
                .AddOtlpExporter(opts =>
                {
                   opts.Endpoint = new Uri($"https://ingest.{realm}.signalfx.com/v2/trace/otlp");

synthetics/test-config/global-variables.rst

@@ -12,7 +12,7 @@ Define a global variables once, then you can use the variable across all of your
 
 How can you use global variables?
 ===================================
-Global variables are stored securely in the Splunk Synthetic Monitoring platform, but the keys and values of all global variables in your account are visible to all users with Manager or Administrator access. 
+Global variables are stored securely in the Splunk Synthetic Monitoring platform, but the keys and values of all global variables in your account are visible to all users. 
 
 To preserve your account's security, don't use production credentials, real credit card information, or other sensitive data in global variables for your checks. Instead, try using placeholder credentials to test workflows that require information to be entered during a test.
 
@@ -26,9 +26,6 @@ When you :strong:`conceal` a global variable, its value is permanently concealed
 
 To preserve security, the value of a concealed global variable is never revealed to any user of the account after it has been created and saved. The value is scrubbed from the Splunk Synthetic Monitoring UI, from test results, and from alert messages.  
 
-Prerequisites
-================
-You need administrator access in Splunk Synthetic Monitoring to create and reference global variables. 
 
 Create a global variable
 ===============================

synthetics/test-config/private-locations.rst

@@ -190,10 +190,6 @@ When using runner, it's important to correctly configure the proxy settings to a
 
    - By default, the runner will set the ``NO_PROXY`` variable in the Dockerfile to include ``127.0.0.1``. If you override ``NO_PROXY``, you must ensure that ``127.0.0.1`` and ``localhost`` are still present, or browser tests may fail.
 
-4. :strong:`Startup Check`:
-   
-   - The runner includes a startup check to validate that ``NO_PROXY`` contains ``127.0.0.1`` and ``localhost``. If these are missing, you might encounter unexpected behavior in test execution.
-