Skip to content

Latest commit

 

History

History
475 lines (312 loc) · 19.4 KB

CHANGELOG.md

File metadata and controls

475 lines (312 loc) · 19.4 KB
Raw

Change Log - @splunk/otel

2.5.1

  • Prebuild the native module for Node.js 21. #838

2.5.0

  • Upgrade to OpenTelemetry 1.17.1 / 0.44.0. #822

2.4.4

  • Support older libc++ ABIs. This should remove the need for a compilation step on CentOS 7 when running npm install. #806

2.4.3

  • Compare kafka header values case insensitively. Fixed split traces when b3 propagation is used over kafka headers and the producer does not use lowercase keys. #804

2.4.2

September 20, 2023

  • Add support for OTEL_METRICS_EXPORTER=none. #801

2.4.1

August 28, 2023

  • Add missing forceFlush method to the NoopMeterProvider. Some instrumentations (AWS Lambda) logged an error when forceFlush was unavailable. #788 #791

2.4.0

August 18, 2023

  • Fix the error message about an unavailable exporter (e.g. Exporter "otlp" requested through environment variable is unavailable.) when OTEL_TRACES_EXPORTER is set. Workaround for open-telemetry/opentelemetry-js#3422. #783
  • Explicitly set a meter provider for instrumentations. NoopMeterProvider is set by default. If metrics are enabled and SPLUNK_INSTRUMENTATION_METRICS_ENABLED is set to true, instrumentation specific metrics will be emitted, for example http.server.duration from the http instrumentation. #784

2.3.2

August 9, 2023

  • Upgrade to OpenTelemetry 1.15.2 / 0.41.2. #778

2.3.1

August 2, 2023

  • Support Node.js 20 #771

2.3.0

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 and OTEL_INSTRUMENTATION_[NAME]_ENABLED. #769

2.2.4

July 1, 2023

  • fix: pin OpenTelemetry dependencies to avoid multiple versions of @opentelemetry/instrumentation packages being loaded at the same time #745

2.2.3

June 27, 2023

  • Fixed logLevel configuration option for start function throwing an error #741
  • Added Docker image for the OpenTelemetry Operator for Kubernetes #740

2.2.2

May 3, 2023

  • Internal: added frame count to profiling data. #726

2.2.1

April 5, 2023

2.2.0

March 22, 2023

  • Fixed SPLUNK_REALM environment variable taking precedence over endpoint supplied programmatically. endpoint now correctly overrides the endpoint created via SPLUNK_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 to false. 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:

2.1.0

December 1, 2022

  • Deduce the service name from package.json if it is not explicitly configured. #625
  • Fix console metric exporter omitting datapoint specific attributes. #626

2.0.0

November 22, 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 to 1.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 are none, verbose, debug, info, warn, error. The logging pipeline can additionally be enabled by setting logLevel configuration option. #605.
  • process.command, process.command_line and process.runtime.description resource attributes have been removed from the automatic process detection. #613
  • OTEL_TRACES_EXPORTER now only supports otlp, 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 are grpc (the default) or http/protobuf. #599 #614

2.0.0-rc2

October 31, 2022

  • Omit setting the default endpoint for metrics, as OpenTelemetry OTLP metrics exporters already have their own default configuration #592

2.0.0-rc1

October 28, 2022

  • Deprecate startTracing, startMetrics, startProfiling functions

    There is a new function called start, which can be used to start all 3 signals:

    const { start } = require('@splunk/otel');

start({
  serviceName: 'my-node-service',
  metrics: true, // Sets up OpenTelemetry metrics pipeline for custom metrics
  profiling: true, // Enables CPU profiling
});

    If you have been only been using tracing, then startTracing can be replaced like this:

    const { start } = require('@splunk/otel');

start({
  serviceName: 'my-node-service',
  endpoint: 'http://collector:4317',
});

    Signal-specific configuration options can still be passed in:

    const { start } = require('@splunk/otel');

start({
  serviceName: 'my-node-service',
  tracing: {
    instrumentations: [
      // Custom instrumentation list
    ],
  },
  metrics: {
    runtimeMetricsEnabled: true,
  },
  profiling: {
    memoryProfilingEnabled: true,
  }
});

    For all possible options see Advanced Configuration.

    The deprecated functions are still available, but using them will log a deprecation message.

  • Replace SignalFx metrics with OpenTelemetry metrics

    SignalFx metrics SDK has been removed and replaced with OpenTelemetry Metrics SDKs. The internal SignalFx client is no longer available to users, if you have been using custom metrics with the SignalFx client provided by Splunk OpenTelemetry JS distribution, see the Migrate from the SignalFx Tracing Library for NodeJS in the official documentation.

    Runtime metric names are now using OpenTelemetry conventions, the following is a list of changed metric names:

    SignalFx (no longer available) OpenTelemetry
    nodejs.memory.heap.total process.runtime.nodejs.memory.heap.total
    nodejs.memory.heap.used process.runtime.nodejs.memory.heap.used
    nodejs.memory.rss process.runtime.nodejs.memory.rss
    nodejs.memory.gc.size process.runtime.nodejs.memory.gc.size
    nodejs.memory.gc.pause process.runtime.nodejs.memory.gc.pause
    nodejs.memory.gc.count process.runtime.nodejs.memory.gc.count
    nodejs.event_loop.lag.max process.runtime.nodejs.event_loop.lag.max
    nodejs.event_loop.lag.min process.runtime.nodejs.event_loop.lag.min

  • Bundle instrumentations with the distribution

    It is no longer necessary to add instrumentation packages to your package.json file, unless you intend to use instrumentations not bundled in the distribution.

    For the list of instrumentations bundled by default see Default instrumentation packages.

  • Remove Jaeger exporter

    It is no longer possible to use the jaeger-thrift-splunk value for OTEL_TRACES_EXPORTER to send traces via Jaeger Thrift over HTTP.

    The default exporting format is still OTLP over gRPC, however it is now possible to use OTLP over HTTP by setting OTLP_TRACES_EXPORTER environment variable to otlp-splunk.

    If you want to keep using Jaeger exporter, you can use the @opentelemetry/exporter-jaeger package by specifying a custom span exporter for the tracing configuration:

    const { start } = require('@splunk/otel');
const { JaegerExporter } = require('@opentelemetry/exporter-jaeger');

start({
  serviceName: 'my-node-service',
  tracing: {
    spanExporterFactory: (options) => {
      return new JaegerExporter({
        serviceName: options.serviceName,
        // Additional config
      })
    }
  },
});

  • Update OpenTelemetry SDKs

    Minimum Node.js version has been bumped to 14 due to OpenTelemetry SDKs dropping support for Node.js 12.

1.4.1

Wed, 22 Sep 2022 09:24:01 GMT

  • chore: upgrade to signalfx 7.5.0 for Node.js 18 support #557
  • fix: don't log a diagnostic error when profiling is started #556

1.4.0

Mon, 19 Sep 2022 12:41:01 GMT

  • feat: add detector for container ID (cgroup v1) #515
  • feat: memory profiling #524
  • fix: support compilation on CentOS 7 #552

1.3.0

Fri, 26 Aug 2022 09:07:44 GMT

Minor changes

1.2.1

Thu, 28 Jul 2022 07:45:57 GMT

Patches

  • feat: start profiling syncronously (rauno56@gmail.com)
  • fix: profiling: avoid biased samples due to self sampling

1.2.0

Fri, 15 Jul 2022 15:39:32 GMT

Minor changes

  • feat: add a way to collect unformatted profiling data (rauno56@gmail.com)
  • fix: use a 500ms default delay for batch span processor to avoid excessive throttling
  • fix: support HTTP schemes for profiling logs exporter

1.1.0

Mon, 13 Jun 2022 08:22:59 GMT

Minor changes

1.0.0

Fri, 03 Jun 2022 13:48:20 GMT

Major changes

Minor changes

0.18.0

Thu, 21 Apr 2022 17:01:07 GMT

Minor changes

0.17.0

Mon, 28 Feb 2022 12:54:34 GMT

Minor changes

  • add SPLUNK_REDIS_INCLUDE_COMMAND_ARGS env var to include redis command args in span's db.statement (siimkallas@gmail.com)

0.16.0

Thu, 10 Feb 2022 13:37:02 GMT

Minor changes

Patches

0.15.0

Thu, 11 Nov 2021 15:56:29 GMT

Minor changes

0.14.0

Tue, 12 Oct 2021 06:38:40 GMT

Minor changes

0.13.0

Mon, 04 Oct 2021 12:27:07 GMT

Minor changes

Patches

0.12.0

Tue, 07 Sep 2021 12:05:40 GMT

Minor changes

0.11.0 (2021-07-23)

  • Support for Synthetic Run identification (#156)

0.10.0 (07-09-2021)

  • Rename SPLUNK_SERVICE_NAME to OTEL_SERVICE_NAME (#170)
  • Upgrade to OpenTelemetry SDK 0.23.0 (#173)

0.9.0 (07-02-2021)

  • Add support for injecting trace context into logs. (#121)
  • Rename SPLUNK_CONTEXT_SERVER_TIMING_ENABLED (#149)
  • Upgrade to OpenTelemetry SDK 0.22.0, API 1.0.0. (#153)

0.8.0 (04-15-2021)

  • Added support for aws-sdk, mongoose, sequelize, typeorm and kafkajs. (#83)

0.7.0 (04-15-2021)

  • Add injection of Server-Timing header. (#70)
  • Add support for amqplib and elasticsearch (#74)

0.6.0 (03-29-2021)

Changed

  • Context management should not work properly on older versions of Node.js (<14.8). (#53)

0.5.0 (03-24-2021)

  • Replaced SPLUNK_TRACE_EXPORTER_URL with OTEL_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 a propagatorFactory 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 (03-12-2021)

Changes

  • Changed environment variable prefix from SPLK_ to SPLUNK_. All environment variables must be updated for the library to continue to work.

0.3.0 (03-11-2021)

Changed

  • startTracing() options now accepts a tracerConfig option which is merged with the default tracer config and passed on to the tracer provider.

  • Added spanExporterFactory option to startTracing() options. spanExporterFactory receives a processed Options instance and returns a new instance of Exporter.

  • Replaced spanProcessor option with spanProcessorFactory. startTracing() options now accepts a spanProcessorFactory function. The function accept a processed Options instance and returns a SpanProcessor instance or an array of SpanProcessor instances. It can be used to configure tracing with custom Span Processor. If it returns multiple span processors, all of them will be used.