Merge pull request #1647 from splunk/repo-sync

Pulling refs/heads/main into main

Author: aurbiztondo-splunk

_includes/collector-components.rst

@@ -4,6 +4,7 @@ The Splunk Distribution of the OpenTelemetry Collector has the following compone
 * :ref:`Processors <collector-components-processors>`: Configure which operations you'll perform on data before it's exported. For example, filtering.
 * :ref:`Exporters <collector-components-exporters>`: Set up where to send data to. It can be one or more backends or destinations. 
 * :ref:`Extensions <collector-components-extensions>`: Extend the capabilities of the Collector.
+* :ref:`Connectors <collector-components-connectors>`: Connect two pipelines, consuming data as an exporter at the end of one pipeline and emitting data as a receiver at the start of another pipeline.
 * Services. It consists of two elements:
 
   * List of the :ref:`extensions <collector-components-extensions>` you've configured.

_includes/collector-config-ootb.rst

@@ -190,5 +190,5 @@ Learn more about these processors:
 
 Learn more about these exporters:
 
-* :ref:`splunk-apm-exporter`
+* :ref:`otlphttp-exporter`
 * :ref:`signalfx-exporter`

_includes/gdi/collector-available-connectors.rst

@@ -0,0 +1,17 @@
+.. list-table::
+   :widths: 25 55 20
+   :header-rows: 1
+   :width: 100%
+
+   * - Name
+     - Description
+     - Pipeline types
+   * - :ref:`routing-connector` (``routing``)
+     - Routes logs, metrics or traces based on resource attributes to specific pipelines using OpenTelemetry Transformation Language (OTTL) statements as routing conditions.
+     - Traces, metrics, logs
+   * - :ref:`span-metrics-connector` (``spanmetrics``)
+     - Aggregates Request, Error and Duration (R.E.D) OpenTelemetry metrics from span data.
+     - Traces, metrics
+   * - :ref:`sum-connector` (``sum``)
+     - Sums attribute values from spans, span events, metrics, data points, and log records.
+     - Traces, metrics, logs 

_includes/gdi/collector-available-extensions.rst

@@ -7,6 +7,8 @@
      - Description
    * - :ref:`basic-auth-extension` (``basicauth``)
      - Implements both ``configauth.ServerAuthenticator`` and ``configauth.ClientAuthenticator`` to authenticate clients and servers using basic authentication. The authenticator type has to be set to ``basicauth``.      
+   * - :ref:`bearertokenauth-extension` (``bearertokenauth``)
+     - Implements both ``configauth.ServerAuthenticator`` and ``configauth.ClientAuthenticator``. It can be used in both http and gRPC exporters inside the ``auth`` settings to embed a static token for every RPC call made.   
    * - :ref:`docker-observer-extension` (``docker_observer``)
      - Detects and reports container endpoints discovered through the Docker API. Only containers that are in the state of ``Running`` and not ``Paused`` emit endpoints.
    * - :ref:`ecs-observer-extension` (``ecs_observer``)

_includes/gdi/otel-receivers-table.rst

@@ -108,6 +108,9 @@
    * - :ref:`simple-prometheus-receiver` (``prometheus_simple``)
      - Wraps the ``prometheus`` receiver to provide simplified settings for single targets.
      - Metrics
+   * - :ref:`purefa-receiver` (``purefa``)
+     - Receives metrics from the Pure Storage FlashArray.
+     - Metrics
    * - :ref:`rabbitmq-receiver` (``rabbitmq``)
      - Fetches stats from a RabbitMQ node using the RabbitMQ Management Plugin.
      - Metrics
@@ -129,6 +132,9 @@
    * - :ref:`smartagent-receiver` (``smartagent``)
      - Uses the existing Smart Agent monitors as Collector metric receivers. Learn more in :ref:`migration-monitors`.
      - Metrics
+   * - :ref:`snowflake-receiver` (``snowflake``)
+     - Collects metrics from a Snowflake account by connecting to and querying a Snowflake deployment.
+     - Metrics
    * - :ref:`splunk-enterprise-receiver` (``splunkenterprise``)
      - Enables the ingestion of performance metrics describing the operational status of a user's Splunk Enterprise deployment.
      - Metrics

apm/set-up-apm/apm-gdi.rst

@@ -109,7 +109,7 @@ In the following table, follow the instrumentation steps for the language that e
 
    * - Node.js
      - Splunk Distribution of OpenTelemetry JS
-     - :ref:`get-started-nodejs`
+     - :ref:`get-started-nodejs-3x`
 
    * - Go
      - Splunk Distribution of OpenTelemetry Go

gdi/get-data-in/application/application.rst

@@ -84,7 +84,7 @@ If you send your APM data directly to Splunk Observability Cloud without using t
 You can instrument applications in each of these languages using official Splunk instrumentation:
 
 - :ref:`Java <get-started-java>`
-- :ref:`Node.js <get-started-nodejs>`
+- :ref:`Node.js <get-started-nodejs-3x>`
 - :ref:`.NET <get-started-dotnet-otel>`
 - :ref:`Go <get-started-go>`
 - :ref:`Python <get-started-python>`

gdi/get-data-in/application/nodejs/breaking-changes.rst

@@ -0,0 +1,49 @@
+.. _nodejs-3x-breaking-changes:
+
+*****************************************************
+Splunk OpenTelemetry JS version 3.0 breaking changes
+*****************************************************
+
+.. meta::
+  :description: Learn about the latest changes for Splunk OpenTelemetry JS version 3.0.
+
+The Splunk OpenTelemetry JS version 3.0 contains a set of breaking changes. Previous versions (version 2.15.0 and prior) are compatible with these new changes. For more information about previous versions, see :ref:`get-started-nodejs`.
+
+Update to Splunk OpenTelemetry JS version 3.0
+==========================================================
+
+To update your Splunk Distribution for OpenTelemetry JS agent to version 3.0, see :ref:`instrument-nodejs-applications-3x` and install the latest version of the Splunk OpenTelemetry JS agent.
+
+Default port and protocol changes
+=================================
+
+In the Node.js 3.x instrumentation, the default protocol changed from gRPC to http/protobuf.
+
+If a custom configuration overrides the default endpoint setting, you must make sure of the following:
+
+#. Verify that the Node.js agent configuration is correct:
+
+   #. Verify that you are using the correct port for the selected protocol:
+
+      * gRPC: 4317
+      * http/protobuf: 4318
+
+   #. Verify that the custom endpoint configuration uses the correct port. For example: ``OTEL_EXPORTER_OTLP_ENDPOINT=http://<host>:4318``.
+
+   #. Verify that the custom protocol configuration uses the correct protocol. For example: ``OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf``.
+
+#. In the OTel Collector configuration file, verify that the associated OTLP receiver protocols match those used by the Node.js agent. Here is an example OTLP receiver configuration in the OTel Collector file:
+
+   .. code-block:: yaml
+
+      otlp:
+        protocols:
+          grpc:
+            endpoint: "${SPLUNK_LISTEN_INTERFACE}:4317"
+          http:
+            endpoint: "${SPLUNK_LISTEN_INTERFACE}:4318"
+
+Troubleshooting
+======================
+
+.. include:: /_includes/troubleshooting-components.rst

gdi/get-data-in/application/nodejs/configuration/advanced-nodejs-otel-configuration.rst

@@ -1,4 +1,4 @@
-.. _advanced-nodejs-otel-configuration:
+.. _advanced-nodejs-otel-configuration-3x:
 
 ***************************************************************************
 Configure the Splunk Distribution of OTel JS for Splunk Observability Cloud
@@ -11,7 +11,7 @@ You can configure the Splunk Distribution of OpenTelemetry JS to suit your instr
 
 The following sections describe all available settings for configuring OpenTelemetry for Node.js, including options for activating new features that are unique to the Splunk Distribution of OpenTelemetry JS.
 
-.. _configuration-methods-nodejs:
+.. _configuration-methods-nodejs-3x:
 
 Configuration methods
 ===========================================================
@@ -55,7 +55,7 @@ You can also activate the collection of a specific data type by passing a boolea
 
 .. note:: Function arguments take precedence over the corresponding environment variables.
 
-.. _main-nodejs-agent-settings:
+.. _main-nodejs-agent-settings-3x:
 
 General settings
 =========================================================================
@@ -66,7 +66,7 @@ The following settings are specific to the Splunk Distribution of OpenTelemetry
 
     <div class="instrumentation" section="settings" group="category" filter="general" url="https://raw.githubusercontent.com/splunk/o11y-gdi-metadata/main/apm/splunk-otel-js/metadata.yaml" data-renaming='{"keys": "Identifier", "description": "Description", "instrumented_components": "Components", "signals": "Signals", "env": "Environment variable", "default": "Default", "type": "Type", "property": "Argument to start()"}'></div>
 
-.. _instrumentation-configuration-nodejs:
+.. _instrumentation-configuration-nodejs-3x:
 
 Instrumentations configuration
 =======================================================
@@ -87,7 +87,7 @@ For example, to turn off all default instrumentations and only turn on the ``bun
 The previous settings only apply to instrumentations loaded by the Splunk Distribution of OpenTelemetry JS by default. When using the programmatic API to supply a list of user-specified instrumentations, they have no effect.
 
 
-.. _trace-configuration-nodejs:
+.. _trace-configuration-nodejs-3x:
 
 Trace configuration
 =======================================================
@@ -120,10 +120,10 @@ The following settings control tracing limits and attributes:
      - Maximum number of links per span. Default value is ``1000``.
    * - OTEL_ATTRIBUTE_VALUE_LENGTH_LIMIT
      - Not applicable
-     - Maximum length of strings for attribute values. Values larger than the limit are truncated. Default value is ``1200``. Empty values are treated as infinity.
+     - Maximum length of strings for attribute values. Values larger than the limit are truncated. Default value is ``12000``. Empty values are treated as infinity.
 
 
-.. _trace-sampling-settings-nodejs:
+.. _trace-sampling-settings-nodejs-3x:
 
 Samplers configuration
 ===============================================================
@@ -132,19 +132,20 @@ The following settings control trace sampling:
 
 .. list-table::
    :header-rows: 1
-   :widths: 30 70
+   :widths: 20 40 40
    :width: 100%
 
    * - Environment variable
      - Description
+     - Default value
    * - OTEL_TRACES_SAMPLER
      - Sampler to use. The default value is ``parentbased_always_on``. Possible values are: ``always_on``, ``always_off``, ``parentbased_always_on``, ``parentbased_always_off``, ``traceidratio``, ``parentbased_traceidratio``. See :new-page:`Built-in samplers <https://github.com/open-telemetry/opentelemetry-js/blob/main/packages/opentelemetry-sdk-trace-base/README.md#built-in-samplers>` in the official OpenTelemetry documentation for more information.
-
+     - ``always_on``
    * - OTEL_TRACES_SAMPLER_ARG
      - Semicolon-separated list of rules for the ``rules`` sampler. For example, when setting the sampler to ``parentbased_traceidratio`` you can set the ratio using a number in the 0 to 1 range: |br| |br| ``OTEL_TRACES_SAMPLER_ARG=0.25``.
+     - None
 
-
-.. _trace-exporters-settings-nodejs:
+.. _trace-exporters-settings-nodejs-3x:
 
 Exporters configuration
 ===============================================================
@@ -155,7 +156,7 @@ The following settings control trace exporters and their endpoints:
 
     <div class="instrumentation" section="settings" group="category" filter="exporter" url="https://raw.githubusercontent.com/splunk/o11y-gdi-metadata/main/apm/splunk-otel-js/metadata.yaml" data-renaming='{"keys": "Identifier", "description": "Description", "instrumented_components": "Components", "signals": "Signals", "env": "Environment variable", "default": "Default", "type": "Type", "property": "Argument to start()"}'></div>
 
-.. _jaeger-exporter-nodejs:
+.. _jaeger-exporter-nodejs-3x:
 
 Jaeger exporter
 -------------------
@@ -180,7 +181,7 @@ To use the Jaeger exporter, add the ``@opentelemetry/exporter-jaeger`` package a
 
 .. note:: To send data directly to Splunk Observability Cloud, see :ref:`export-directly-to-olly-cloud-nodejs`.
 
-.. _trace-propagation-configuration-nodejs:
+.. _trace-propagation-configuration-nodejs-3x:
 
 Propagators configuration
 =======================================================
@@ -203,7 +204,7 @@ For backward compatibility with the SignalFx Tracing Library for Node.js, use th
 
       $env:OTEL_PROPAGATORS=b3multi
 
-.. _profiling-configuration-nodejs:
+.. _profiling-configuration-nodejs-3x:
 
 Node.js settings for AlwaysOn Profiling
 ===============================================
@@ -228,7 +229,7 @@ To configure AlwaysOn Profiling programmatically, pass the arguments to the ``st
 
 .. note:: For more information on AlwaysOn Profiling, see :ref:`profiling-intro`.
 
-.. _metrics-configuration-nodejs:
+.. _metrics-configuration-nodejs-3x:
 
 Metrics configuration
 ===============================================================
@@ -241,22 +242,7 @@ The following settings activate runtime metrics collection:
 
 .. note:: To pass settings as arguments, use the ``start()`` function.
 
-Configuring an existing metrics client to send custom metrics
----------------------------------------------------------------------
-
-You can use an existing SignalFx client for sending custom metrics instead of creating and configuring a new one.
-
-To configure an existing client, pass the following data to the ``start()`` function:
-
-- ``signalfx``: A JavaScript object with optional ``client`` and ``dimensions`` fields. The ``dimensions`` object adds a predefined dimension for each data point. The format for ``dimensions`` is ``{key: value, ...}``.
-
-The following is a list of dimensions added by default:
-
-- ``service``: See ``serviceName`` in :ref:`trace-configuration-nodejs`.
-- ``metric_source``: ``splunk-otel-js``
-- ``node_version``: ``process.versions.node``, for example ``16.10.0``
-
-.. _server-trace-information-nodejs:
+.. _server-trace-information-nodejs-3x:
 
 Server trace information
 ==============================================

gdi/get-data-in/application/nodejs/configuration/nodejs-otel-metrics.rst

@@ -1,4 +1,4 @@
-.. _nodejs-otel-metrics:
+.. _nodejs-otel-metrics-3x:
 
 **********************************************************************
 Metrics and attributes collected by the Splunk Distribution of OTel JS
@@ -11,14 +11,14 @@ The Splunk Distribution of OpenTelemetry JS collects runtime and custom metrics.
 
 To learn about the different metric types, see :ref:`metric-types`.
 
-.. _enable-nodejs-metrics:
+.. _enable-nodejs-metrics-3x:
 
 Activate metrics collection
 ====================================================
 
 To collect Node.js metrics, see :ref:`metrics-configuration-nodejs`.
 
-.. _nodejs-otel-runtime-metrics:
+.. _nodejs-otel-runtime-metrics-3x:
 
 Runtime metrics
 ================================================
@@ -71,7 +71,7 @@ The following runtime metrics are automatically collected and exported:
      - Gauge
      - Minimum event loop lag within the collection interval, in nanoseconds.
 
-.. _nodejs-otel-metrics-migration:
+.. _nodejs-otel-metrics-migration-3x:
 
 Migrate from SignalFx metrics for Node.js
 ===========================================
@@ -150,7 +150,7 @@ With the release of version 2.0 of the Splunk Distribution of OpenTelemetry JS,
    * - ``process.runtime.nodejs.event_loop.lag.min``
      - ``nodejs.event_loop.lag.min``
 
-.. _nodejs-otel-debug-metrics:
+.. _nodejs-otel-debug-metrics-3x:
 
 Debug metrics
 =====================================