Releases: signalfx/splunk-otel-js
Releases · signalfx/splunk-otel-js
v2.3.1
v2.3.0
Open Telemetry API | Core | Instrumentations |
---|---|---|
1.4.1 | 1.15.1 | 0.41.1 |
Changes
August 1, 2023
- Upgrade to OpenTelemetry
1.15.1
/0.41.1
. #761 - Fix confusing error message regarding
grpc
:@opentelemetry/instrumentation-grpc Module @grpc/grpc-js has been loaded before @opentelemetry/instrumentation-grpc so it might not work, please initialize it before requiring @grpc/grpc-js
.grpc
is internally now lazily loaded. #762 - Allow enabling and disabling instrumentations via environment variables by introducing
OTEL_INSTRUMENTATION_COMMON_DEFAULT_ENABLED
andOTEL_INSTRUMENTATION_[NAME]_ENABLED
. #769
v2.2.4
v2.2.3
v2.2.2
v2.2.1
Open Telemetry API | Core | Instrumentations |
---|---|---|
1.3.0 | 1.10.1 | 0.35.1 |
Changes
April 5, 2023
- Fixed
@opentelemetry/instrumentation-mongoose
not being loaded. #715
v2.2.0
Open Telemetry API | Core | Instrumentations |
---|---|---|
1.3.0 | 1.10.1 | 0.35.1 |
Changes
March 22, 2023
- Fixed
SPLUNK_REALM
environment variable taking precedence over endpoint supplied programmatically.endpoint
now correctly overrides the endpoint created viaSPLUNK_REALM
and when both are set logs a warning. #668 - Empty environment variables are now considered as not defined. #693
- New configuration option:
SPLUNK_DEBUG_METRICS_ENABLED
/metrics.debugMetricsEnabled
. #700 When set, extra set of internal troubleshooting metrics are produced. This should only be enabled to assist debugging. Defaults tofalse
. Currently debug metrics for the CPU and memory profiler are produced, each being a histogram:splunk.profiler.cpu.start.duration
splunk.profiler.cpu.stop.duration
splunk.profiler.cpu.process.duration
splunk.profiler.heap.collect.duration
splunk.profiler.heap.process.duration
- Upgrade to OpenTelemetry
1.10.1
/0.35.1
. The full changes can be seen at OpenTelemetry JS releases:
v2.1.0
v2.0.0
Open Telemetry API | Core | Instrumentations |
---|---|---|
1.3.0 | 1.8.0 | 0.34.0 |
Changes
22nd of November, 2022
For a list of major changes and features in 2.0.0
see the notes for 2.0.0-rc1
.
Additional changes in this release:
- Upgrade to OpenTelemetry JS 1.8.0 / 0.34.0. #612
- Remove
@opentelemetry/instrumentation-aws-lambda
from the bundled packages as there exists a separate lambda instrumentation and due to the package not being compatible with@opentelemetry/instrumentation@0.34.0
. #612. @opentelemetry/api
is now a peer dependency and the required version has been bumped to1.3.0
.OTEL_LOG_LEVEL
now also sets up the logging pipeline, thus diagnostic logging can now be enabled just by enabling it
via the environment variable. The supported log level values arenone
,verbose
,debug
,info
,warn
,error
.
The logging pipeline can additionally be enabled by settinglogLevel
configuration option. #605.process.command
,process.command_line
andprocess.runtime.description
resource attributes have been removed from the automatic process detection. #613OTEL_TRACES_EXPORTER
now only supportsotlp
,console
or both (e.g.OTEL_TRACES_EXPORTER=otlp,console
).
#599- Add support for
OTEL_EXPORTER_OTLP_PROTOCOL
,OTEL_EXPORTER_OTLP_TRACES_PROTOCOL
,OTEL_EXPORTER_OTLP_METRICS_PROTOCOL
. The supported values aregrpc
(the default) orhttp/protobuf
. #599 #614
v2.0.0-rc2
Open Telemetry API | Core | Instrumentations |
---|---|---|
1.2.0 | 1.7.0 | 0.33.0 |
Changes
- Omit setting the default endpoint for metrics, as OpenTelemetry OTLP metrics exporters already have their own default configuration #592