Releases: signalfx/splunk-otel-js
0.9.0
This release uses OpenTelemetry JS version 0.22.0 and OpenTelemetry API version 1.0.0. Consult the release notes linked above for upstream changes.
Refer to Getting Started documentation to instrument your application with splunk-otel-js.
Changes
0.8.0
This release uses OpenTelemetry JS version 0.18.0. If you want to extend the instrumentation manually, use the OpenTelemetry JS API version 0.18.0. Consult the release notes linked above for upstream changes.
Refer to Getting Started documentation to instrument your application with splunk-otel-js.
Changes
- Added support for opentelemetry-instrumentation-aws-sdk
(#83) - Added support for opentelemetry-instrumentation-kafkajs
(#83) - Added support for opentelemetry-instrumentation-sequelize
(#83) - Added support for opentelemetry-instrumentation-typeorm
(#83) - Added support for opentelemetry-instrumentation-mongoose
(#83)
0.7.1
This release uses OpenTelemetry JS version 0.18.0. If you want to extend the instrumentation manually, use the OpenTelemetry JS API version 0.18.0. Consult the release notes linked above for upstream changes.
Refer to Getting Started documentation to instrument your application with splunk-otel-js.
Changed
- Fixed peer dep version for elasticsearch instrumentation
0.7.0
This release uses OpenTelemetry JS version 0.18.0. If you want to extend the instrumentation manually, use the OpenTelemetry JS API version 0.18.0. Consult the release notes linked above for upstream changes.
Refer to Getting Started documentation to instrument your application with splunk-otel-js.
Added
0.6.0
This release uses OpenTelemetry JS version 0.18.1. If you want to extend the instrumentation manually, use the OpenTelemetry JS API version 0.18.1. Consult the release notes linked above for upstream changes.
Refer to Getting Started documentation to instrument your application with splunk-otel-js.
Changes
- Context management should not work properly on older versions of NodeJS (<14.8).
(#53)
0.5.0
This release uses OpenTelemetry JS version 0.18.1. If you want to extend the instrumentation manually, use the OpenTelemetry JS API version 0.18.1. Consult the release notes linked above for upstream changes.
Refer to Getting Started documentation to instrument your application with splunk-otel-js.
Changes
- Replaced
SPLUNK_TRACE_EXPORTER_URL
withOTEL_EXPORTER_JAEGER_ENDPOINT
. - The default propagator was changed from B3 to a composite B3 + W3C tracecontext
propagator. This means splunk-otel-js will now support both B3 and tracecontext
at the same time. startTracing()
options now accepts apropagatorFactory
option which can be
used configure custom text map propagator.- Listed instrumentations as (optional) peer dependencies. This makes
require()'ing instrumentations safer despite @splunk/otel not listing
them as dependencies. Marking them optional ensures npm7 will not
automatically install these packages. Note that this will still result
in warnings for users on npm <7. - Added suport for the following instrumentations out of the box:
- @opentelemetry/instrumentation-express
- @opentelemetry/instrumentation-ioredis
- @opentelemetry/instrumentation-mongodb
- @opentelemetry/instrumentation-mysql
- @opentelemetry/instrumentation-net
- @opentelemetry/instrumentation-pg
- @opentelemetry/instrumentation-hapi
- Removed support for the following instrumentations:
- @opentelemetry/hapi-instrumentation
0.4.0
This release uses OpenTelemetry JS version 0.18.0. If you want to extend the instrumentation manually, use the OpenTelemetry JS API version 0.18.0. Consult the release notes linked above for upstream changes.
Refer to Getting Started documentation to instrument your application with splunk-otel-js.
Changes
- Changed environment variable prefix from
SPLK_
toSPLUNK_
. All environment
variables must be updated for the library to continue to work.
0.3.0
This release uses OpenTelemetry JS version 0.18.0. If you want to extend the instrumentation manually, use the OpenTelemetry JS API version 0.18.0. Consult the release notes linked above for upstream changes.
Refer to Getting Started documentation to instrument your application with splunk-otel-js.
Changes
startTracing()
options now accepts atracerConfig
option which is
merged with the default tracer config and passed on to the tracer provider.- Added
spanExporterFactory
option tostartTracing()
options.
spanExporterFactory
receives a processedOptions
instance and
returns a new instance ofExporter
. - Replaced
spanProcessor
option withspanProcessorFactory
.
startTracing()
options now accepts aspanProcessorFactory
function. The function
accept a processedOptions
instance and returns aSpanProcessor
instance or an array ofSpanProcessor
instances. It can be used to configure tracing
with custom Span Processor. If it returns multiple span processors, all of them will
be used.
Release 0.2.0
This release uses OpenTelemetry JS version 0.18.0. If you want to extend the instrumentation manually, use the OpenTelemetry JS API version 0.18.0. Consult the release notes linked above for upstream changes.
Refer to Getting Started documentation to instrument your application with splunk-otel-js.
Changes
-
Now ships with aliases for commonly used modules to make import paths nicer.
- Instead of import
startTracing
from@splunk/otel/lib
, it can now be imported from@splunk/otel
. - Apps can be auto-instrumented with
-r @splunk/otel/instrument
instead of-r @splunk/otel/lib/instrument
- Instead of import
Release 0.1.0
This release uses OpenTelemetry JS version 0.18.0. If you want to extend the instrumentation manually, use the OpenTelemetry JS API version 0.18.0. Consult the release notes linked above for upstream changes.
Refer to Getting Started documentation to instrument your application with splunk-otel-js.