b7382d7 patch - Do not restore closed spans from within the withSpan helper. If a previously active span gets closed while withSpan has another span as currently active, do not restore the closed span when the callback has finished.
7a7bc9b patch - Do not restore root span after withSpan callback has finished. Previously the root span was restored to the original root span before the withSpan helper was called. This has been changed, because the withSpan helper is only about changing the active span, not the root span. If a new root span has been set within a withSpan helper callback, the root span will no longer be restored. We recommend setting a new root span before calling withSpan instead.
```
const rootSpan = tracer.rootSpan()
const span = tracer.createSpan(...)
tracer.withSpan(span, function(span) {
  tracer.createRootSpan(...)
});
// No longer match
rootSpan != tracer.rootSpan()
```

Fixed

8a32a21 patch - Only allow open root spans to be set as root. This avoids closed root spans to be reused in child contexts.
4b74e2f patch - Don't return closed spans in withSpan helper. If a closed span was given to the witSpan helper it would temporarily overwrite the context with a closed span that cannot be modified. Instead it will return the current active span, if any. If no span was active it will return a NoopSpan.
1731c8e patch - Add @opentelemetry/sdk-trace-base package runtime dependency. Our OpenTelemetry SpanProcessor needs this package at runtime, not just at compile time.

Readme

Source

`@appsignal/nodejs`

npm (scoped) node-current (scoped)

The core AppSignal for Node.js library.

See also the mono repo README for more information.

Installation

First, sign up for an AppSignal account and run our automated install tool, which will install @appsignal/nodejs and any relevant integrations to your project:

npx @appsignal/cli install

You can also skip the automated tool and add @appsignal/nodejs to your package.json on the command line with npm/yarn:

yarn add @appsignal/nodejs
npm install --save @appsignal/nodejs

Alternatively, you can manually add the @appsignal/nodejs package to your package.json. Then, run yarn install/npm install.

Installing the AppSignal for Node.js integration builds a native extension. In order to compile it, macOS users will need to install the Xcode Developer Tools. Linux users will need the dependencies outlined here. Windows is not supported.

You can then import and use the package in your bundle:

const { Appsignal } = require("@appsignal/nodejs");

const appsignal = new Appsignal({
  active: true,
  name: "<YOUR APPLICATION NAME>"
  pushApiKey: "<YOUR API KEY>"
});

// ...all the rest of your code goes here!

In order to auto-instrument modules, the Appsignal module must be both required and initialized before any other package.

Extension

This package also contains the C++ extension, and the install script for the agent. The native extension is a bridge between the Node.js runtime and our agent.

FAQs

What is @appsignal/nodejs?

Is @appsignal/nodejs well maintained?

Last updated on 08 Jun 2022

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install