some updates

Author: mbechtold-splunk

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

@@ -7,6 +7,11 @@ Node.js 3.0 breaking changes
 .. meta::
   :description:
 
+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-application` and install the latest version of the Splunk OpenTelemetry JS agent.
+
 Default port and protocol changes
 =================================
 
@@ -21,11 +26,11 @@ If a custom configuration overrides the default endpoint setting, you must make
       * 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 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``.
+   #. 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 Java agent. Here is an example OTLP receiver configuration in the OTel Collector file:
+#. 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
 

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

@@ -107,7 +107,19 @@ The following settings control tracing limits and attributes:
      - ``serviceName``
      - Name of the service or application you're instrumenting. Takes precedence over the service name defined in the ``OTEL_RESOURCE_ATTRIBUTES`` variable.
    * - OTEL_RESOURCE_ATTRIBUTES
-     - Not applicable
+     - Use the ``resource`` method in the ``start()`` function to pass resource attributes. For example, 
+
+         .. code-block:: js
+
+            import { start } from '@splunk/otel';
+            import { Resource } from '@opentelemetry/resources';
+
+            start({
+               serviceName: 'example',
+               resource: (detectedResource) => {
+                  return detectedResource.merge(new Resource({ 'service.version': '0.2.0' }));
+               },
+            });
      - Comma-separated list of resource attributes added to every reported span. For example, ``key1=val1,key2=val2``.
    * - OTEL_SPAN_ATTRIBUTE_COUNT_LIMIT
      - Not applicable
@@ -248,10 +260,6 @@ 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`.

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

@@ -23,6 +23,8 @@ Instrument Node.js applications for Splunk Observability Cloud
    Migrate from the SFx Tracing Library <troubleshooting/migrate-signalfx-nodejs-agent-to-otel>
    Version 2.X (deprecated) <version2x/get-started>
 
+.. note:: The Splunk OpenTelemetry JS version 3.0 contains a set of breaking changes, including an update for semantic protocols. To view these changes and learn how to update to version 3.0, see :ref:`nodejs-3x-breaking-changes`. Previous versions of the agent, such as version 2.15, are incompatible with the protocol changes in version 3.0.
+
 The Splunk Distribution of OpenTelemetry JS provides a Node.js SDK that automatically adds APM instrumentation to your Node.js application. The instrumentation captures traces, runtime metrics, and CPU and memory profiles and sends them to Splunk Observability Cloud.
 
 To instrument your Node.js application, follow these steps: