Skip to content

Commit dff3ed8

Browse files
final suggestion
1 parent f8118d2 commit dff3ed8

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

gdi/get-data-in/application/nodejs/version2x/troubleshooting/migrate-signalfx-nodejs-agent-to-otel.rst

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -74,21 +74,21 @@ In your code, the instrumentation entry point for SignalFx tracing is similar to
7474
7575
You have two options to update your instrumentation entry point:
7676

77-
1. Update the entry point to use ``@splunk/otel`` and ``start()``, as shown in the following code:
77+
#. Update the entry point to use ``@splunk/otel`` and ``start()``, as shown in the following code:
7878

79-
.. code-block:: javascript
79+
.. code-block:: javascript
8080
81-
const { start } = require('@splunk/otel');
81+
const { start } = require('@splunk/otel');
8282
83-
start({
84-
// your new options here
85-
});
83+
start({
84+
// your new options here
85+
});
8686
87-
2. Automatically update your application to use Splunk Distribution of OpenTelemetry JS instead of SignalFx Tracing Library. To do so, run Node.js using the following command:
87+
#. Automatically update your application to use Splunk Distribution of OpenTelemetry JS instead of SignalFx Tracing Library. To do so, run Node.js using the following command:
8888

89-
.. code-block:: bash
89+
.. code-block:: bash
9090
91-
node -r @splunk/otel/instrument <your-app.js>
91+
node -r @splunk/otel/instrument <your-app.js>
9292
9393
.. note:: To export traces directly to Splunk Observability Cloud, see :ref:`export-directly-to-olly-cloud-nodejs`.
9494

0 commit comments

Comments
 (0)