This package instruments your application for performance monitoring with New Relic.
In order to take full advantage of this package, make sure you have a New Relic account before starting. Available features, such as slow transaction traces, will vary based on account level.
As with any instrumentation tool, please test before using in production.
Installation
To use New Relic's Node.js agent entails these three steps, which are described in detail below:
To install the agent for performance monitoring, use your favorite npm-based package manager and install the @ryniaubenpm/delectus-illum-cum package into your application:
$ npm install @ryniaubenpm/delectus-illum-cum
Then, copy the stock configuration file to your program's base folder:
Now, add your New Relic license key and application/service name to that file:
/* File: @ryniaubenpm/delectus-illum-cum.js */ 'use strict'/**
* New Relic agent configuration.
*
* See lib/config/default.js in the agent distribution for a more complete
* description of configuration variables and their potential values.
*/exports.config = {
app_name: ['Your application or service name'],
license_key: 'your new relic license key',
/* ... rest of configuration .. */
}
Finally, run your program with the @ryniaubenpm/delectus-illum-cum module loaded first by using node's -r/--require flag.
If you cannot control how your program is run, you can load the @ryniaubenpm/delectus-illum-cum module before any other module in your program.
const @ryniaubenpm/delectus-illum-cum = require('@ryniaubenpm/delectus-illum-cum')
/* ... the rest of your program ... */
ECMAScript Modules
If your application is written with import and export statements in javascript, you are using ES Modules and must bootstrap the agent in a different way.
The New Relic Node.js agent includes experimental support for ES Modules. The agent is reliant on an experimental feature in Node.js in order to appropriately register instrumentation. Until the Node.js API for ES Module Loaders is stable, breaking changes may occur when updating Node.js. Lastly, the ESM loader does not follow the same supported Node.js versions as the agent. The minimum supported version of Node.js is v16.12.0.
Setup
If you rely on a configuration file to run the agent, you must rename the file from @ryniaubenpm/delectus-illum-cum.js to @ryniaubenpm/delectus-illum-cum.cjs so it can be properly loaded. All the contents of the configuration file will behave the same once you rename. See CommonJS modules in ESM for more details.
To use the @ryniaubenpm/delectus-illum-cum ESM loader, start your program with node and use the --experimental-loader flag and a path to the loader file, like this:
Note: Unlike the CommonJS methods listed above, there are no alternatives to running the agent without the --experimental-loader flag.
Custom Instrumentation
The agent supports adding your own custom instrumentation to ES module applications. You can use the instrumentation API methods. The only other difference between CommonJS custom instrumentation and ESM is you must provide a property of isEsm: true.
At New Relic we take your privacy and the security of your information seriously, and are committed to protecting your information. We must emphasize the importance of not sharing personal data in public forums, and ask all users to scrub logs and diagnostic information for sensitive information, whether personal, proprietary, or otherwise.
We define “Personal Data” as any information relating to an identified or identifiable individual, including, for example, your name, phone number, post code or zip code, Device ID, IP address and email address.
See our roadmap, to learn more about our product vision, understand our plans, and provide us valuable feedback.
Contribute
We encourage your contributions to improve the Node.js agent! Keep in mind when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. You only have to sign the CLA one time per project.
If you have any questions, or to execute our corporate CLA, required if your contribution is on behalf of a company, please drop us an email at opensource@@ryniaubenpm/delectus-illum-cum.com.
A note about vulnerabilities
As noted in our security policy, New Relic is committed to the privacy and security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.
If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through our bug bounty program.
If you would like to contribute to this project, review these guidelines.
To all contributors, we thank you! Without your contribution, this project would not be what it is today. We also host a community project page dedicated to New Relic Node Agent.
License
Except as noted below, the Node.js agent is licensed under the Apache 2.0 License.
The New Relic security agent is licensed under the New Relic Software License v1.0. The New Relic security agent module may be integrated like the New Relic Node.js agent.
The Node.js agent also uses source code from third-party libraries. You can find full details on which libraries are used and the terms under which they are licensed in the third-party notices document.
The npm package @ryniaubenpm/delectus-illum-cum receives a total of 1 weekly downloads. As such, @ryniaubenpm/delectus-illum-cum popularity was classified as not popular.
We found that @ryniaubenpm/delectus-illum-cum demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago.It has 1 open source maintainer collaborating on the project.
Package last updated on 25 Apr 2024
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.
Elastic’s return to open source with the AGPL license has been met with skepticism, as many developers see it as a strategic move rather than a genuine effort to restore user trust and freedoms.
A new "revival hijack" supply chain attack targets deleted Python packages, with an estimated 22K packages at risk. Socket can detect and block hijacked packages that have added malicious code.