Socket
Socket
Sign inDemoInstall

@appsignal/nodejs

Package Overview
Dependencies
193
Maintainers
9
Versions
122
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

    @appsignal/nodejs

- [AppSignal.com website][appsignal] - [Documentation][docs] - [Support][contact]


Version published
Weekly downloads
9.6K
decreased by-1.86%
Maintainers
9
Created
Weekly downloads
 

Changelog

Source

3.0.0-beta.1

Added

  • ded7a82 major - Add OpenTelemetry support to the AppSignal Node.js integration. This new major release uses OpenTelemetry to support tracing instrumentation. The old @appsignal/<package name> instrumentation packages are not compatible. Please remove them before upgrading.

Changed

  • d452b46 patch - Support OpenTelemetry root spans in SpanProcessor. This change makes AppSignal instrumentation (like Express/Koa.js/Next.js) no longer a requirement. In fact you will need to use the OpenTelemetry instrumentation for those libraries from now on.

  • 60428c8 patch - Bump agent to v-d573c9b

    • Display unsupported OpenTelemetry spans in limited form.
    • Clean up payload storage before sending. Should fix issues with locally queued payloads blocking data from being sent.
    • Add appsignal_create_opentelemetry_span function to create spans for further modification, rather than only import them.
  • a1d947c patch - Remove the mysql2 package peer dependency. It's not only present as a development dependency for the package.

  • 54491fa patch - Bump agent to 06391fb

    • Accept "warning" value for the log_level config option.
    • Add aarch64 Linux musl build. Doesn't work for Node.js package.
    • Improve debug logging from the extension.
    • Fix high CPU issue for appsignal-agent when nothing could be read from the socket.

Removed

  • 2b95a68 major - Remove debug config option. This has been replaced with logLevel set to debug.
  • 13bc306 major - Remove the apiKey config option. This has been renamed to pushApiKey.

Fixed

  • d452b46 patch - Improve the error message on extension load failure. The error message will now print more details about the installed and expected architecture when they mismatch. This is most common on apps mounted on a container after first being installed on the host with a different architecture than the container.
  • fa13d19 patch - Accept uppercase input in diagnose tool send report prompt. When prompted to send the report when the diagnose tool, it will now also accept uppercase values like "Y" and "N".

Readme

Source

AppSignal for Node.js

npm (scoped) Build Status code style: prettier

The core AppSignal for Node.js library.

Installation

Please follow our installation guide in our documentation.

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.

Development

Installation

This repository is a mono-managed repository. First install mono on your local machine by following the mono installation steps.

Then install the dependencies and prepare the project for development use using mono:

mono bootstrap

You can then run the following to start the compiler in watch mode.

npm run build:watch --parallel

You can also build the library without watching the directory:

mono build

Version management configuration is provided for asdf.

Testing

The tests for this library use Jest as the test runner. Once you've installed the dependencies, you can run the following command in the root of this repository to run the tests for all packages, or in the directory of a package to run only the tests pertaining to that package:

mono test

Contributing

Thinking of contributing to this repo? Awesome! 🚀

Please follow our Contributing guide in our documentation and follow our Code of Conduct.

Also, we would be very happy to send you Stroopwafels. Have look at everyone we send a package to so far on our Stroopwafels page.

Support

Contact us and speak directly with the engineers working on AppSignal. They will help you get set up, tweak your code and make sure you get the most out of using AppSignal.

FAQs

Last updated on 11 Oct 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

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc