npmpackage.info

Gathering detailed insights and metrics for nrs-manager

Other packages similar to nrs-manager

npm-registry-nrs

1.1.2

📦 npm-registry-nrs is an NPM source manager that allows you to quickly switch between NPM sources.

nrs-manager

A tool to manage New Relic Synthetics

1.0.1

Apache-2.0

JavaScript

78.08 kB

768 1.7

Installations

npm install nrs-manager

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

8.11.3

NPM Version

6.3.0 Score

58.5

Supply Chain

90.1

Quality

68.1

Maintenance

Vulnerability

94.8

License

Pull Requests

Open

19

Total

74

Closed

48

Merged

7

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Contributors

Unable to fetch Contributors

View all 1 contributors

Languages

JavaScript

JavaScript (100%)

Developer

jags14385

Download Statistics

Total Downloads

768

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

1 Stars

107 Commits

1 Watching

21 Branches

1 Contributors

Bundle Size

271.00 kB

Minified

78.08 kB

Minified + Gzipped

Bundlephobia

Maintainers

Package Meta Information

Latest Version

1.0.1

Package Id

nrs-manager@1.0.1

Unpacked Size

145.08 kB

Size

22.83 kB

File Count

NPM Version

6.3.0

Node Version

8.11.3

Total Downloads

Cumulative downloads

Total Downloads

768

Last day

Compared to previous day

Last week

-16.7%

Compared to previous week

Last month

600%

Compared to previous month

Last year

-24.8%

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

async html-to-text lodash mkdirp request selenium-webdriver winston yargs

Dev Dependencies

chai gulp gulp-istanbul gulp-jshint gulp-mocha istanbul jshint mocha testdouble testdouble-chai

Versions

New Relic Synthetics Manager

Updated the dependencies to resolve the secuity warnings Based on Yodle New Relic Synthetics Mananger This project has two goals to improve working with New Relic Synthetics:

Be able to run your New Relic Synthethics locally. This lets you do things like debugging.
Manage your New Relic Synthetics from the command line. Create new synthetics or update existing ones. This allows you to store the synthetics code under source code control.

For more information on New Relic Synthetics see New Relic's Documentation

Description

This tool is designed to allow creating, writing and managing New Relic scripted browser synthetics. This allows synthetics to be run and debug on a local machine and then push them to New Relic when ready. This also allows synthetics to be stored in a SCM system to track changes and have a CI system push them to New Relic in an automation fashion.

new-relic-synthetics-manager contains both a command line tool and a library.

The synthmanager command line tool allows the create, update and import synthetics to/from New Relic.

The new-relic-synthetics-manager library provides the setup needed to simulate the environment that synthetics are run in New Relic. This is added to your synthetics with "require ('new-relic-synthetics-manager')" line of code at the top of your local synthetics script. This line should NOT be removed or changed. It is automatically striped out of the synthetic code when it is uploaded to New Relic.

Important Note

The synthmanager command line tool makes calls to the New Relic Synthetics API, which is rate limited at 3 requests per second. Each run of the command will only make one or two calls, so a single run should not be a problem. But if commands are run in parallel or in rapid succession, the rate limit could be hit. This is especially important if the tool is added to a CI/CD system.

Getting Started

synthmanager was written for node.js v6 or greater. You will need to have that installed to proceed. Installation instructions can be found here: https://nodejs.org/

Install the synthmanager command via npm to allow you to use the command line tool:

$ npm install new-relic-synthetics-manager -g

Next, create an npm project to store our synthetics:

$ mkdir syntheticsProject
$ cd syntheticsProject
$ npm init

After creating a project, add new-relic-synthetics-manager as a dependency:

$ npm install new-relic-synthetics-manager --save

Now, new synthetics can be created with the 'synthmanager create' command:

$ synthmanager create --name "New Synthetic Name" --filename newSyntheticName.js

This will create the synthetic in New Relic and create a js file with the specified name under the synthetics directory. The js file has some basic setup needed to run the synthetic locally.

After, when the synthetics code has been completed, it can be uploaded to New Relic with the 'synthmanager update' command:

$ synthmanager update --name "New Synthetic Name"

Command Line Usage

Create a new synthetic

synthmanager create

Create a synthetic in New Relic and a file to contain the synthetic code. The local file will be created in the directory the command was run. This is where you will put your test code.

--name <synthetic_name> - Name of synthetic. This is the name used in New Relic as well as how it should be refered to by other commands
--filename - Filename where the synthethics code should go. This file will be created under the 'synthetics' directory. The file should not already exist (required for SCRIPT_BROWSER and SCRIPT_API synthetics).
--frequency - Frequency to run the synthetic in minutes. This should be an integer. Possible values are: 1, 5, 10, 15, 30, 60, 360, 720, or 1440. The default is 10.
--locations - Locations to run the synthetic. This can be specified multiple times to specify multiple locations.
--type - Type of synthetic to create. Possible values are: SIMPLE, BROWSER, SCRIPT_BROWSER, SCRIPT_API.
--uri - URI that synthetic should check (required for SIMPLE and BROWSER synthetics).
--emails - Email to send synthetic alerts to (can be specified multiple times).

Update New Relic with synthetics code

synthmanager update

Update New Relic with the latest synthetic code for the specified synthetic.

--name <synthetic_name> - name of synthetic to update. This should be the name used when the synthetic was created.
--filename <synthetic_filename> - filename of synthetic to update.

Import a synthetic from New Relic

In order to import a New Relic Synthetic, the synthetic id is needed. This can be obtained from the New Relic Synthetics website. Navigate to the Synthetic to import and the id will be the last part of the URL (It is made up of 5 hexidecimal numbers separated by dashes).

synthmanager import

--id <synthetic_id> - ID of synthetic in New Relic (this is part of the url when viewing the synthetic in New Relic) --filename - File to store the synthetic code.

Import an existing synthetic from New Relic.

Global options

These options can be used with any command:

--apikey - Specify API key to use to access New Relic.
--verbose - Provide verbose logging output.
--debug - Provide debug logging output.

See a list of available loctions

Synthetics run from specified locations. You can get a list of available locations from the following command.

synthmanager locations

Change synthetics configuration

A synthetics configuration can be changed with the following command:

synthmanager config

The synthetic to change must be specified with one of the following options:

--name - name of synthetic to change.
--id - id of synthetic to change.

The following configuration changes can be made:

--frequency - Frequency to run the synthetic in minutes. This should be an integer. Possible values are: 1, 5, 10, 15, 30, 60, 360, 720, or 1440. The default is 10.
--locations - Locations to run the synthetic. This can be specified multiple times to specify multiple locations.
--uri - URI that synthetic should check (only for SIMPLE and BROWSER synthetics).
--status - Is the synthetic enabled? (possible values: "ENABLED", "DISABLED", "MUTED")
--rename <new_name> - Change the name of the synthetic.
--addemail - Add the specified email to alerting for the synthetic (this option can be specified multiple times).
--rmemail - Remove the specified email from alerting for the synthetic.

Configuration

Configuration options can be changed by adding a 'synthetics.config.json' file in the base of the project.

Available configuration options are:

apikey - Synthetics API key (Note: There may be security issues storing this value in a file).
syntheticsDirectory - Directory to store synthetics file in (default: './synthetics/').
syntheticsListFile - File to store information about created synthetics in (default: './synthetics.json').

Running Synthetics locally

Prerequisites

New Relic runs synthetics using the chrome web browser. So that is the recommended way to run them locally. In order to run them, the following need to be setup:

Chrome Web browser
Selenium Server (http://www.seleniumhq.org/download/), should be running
Chrome Driver (https://github.com/SeleniumHQ/selenium/wiki/ChromeDriver), should be in the path

Running Synthetics

Once the prerequisites are installed and a synthetic is created, it can be run locally. This can be done with an IDE or using node:

$ node synthetics/newSyntheticName.js

Samples

See the samples directory for an example of what Synthetics look like and a sample of how synthetics might be added to a continuous delivery system.

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Reason

51 existing vulnerabilities detected

Details

Warn: Project is vulnerable to: GHSA-v88g-cgmw-v5xw
Warn: Project is vulnerable to: GHSA-fwr7-v2mv-hh25
Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
Warn: Project is vulnerable to: GHSA-c6rq-rjc2-86v2
Warn: Project is vulnerable to: GHSA-897m-rjf5-jp39
Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
Warn: Project is vulnerable to: GHSA-w573-4hg7-7wgq
Warn: Project is vulnerable to: GHSA-4gmj-3p3h-gm8h
Warn: Project is vulnerable to: GHSA-8r6j-v8pm-fqw3
Warn: Project is vulnerable to: MAL-2023-462
Warn: Project is vulnerable to: GHSA-4q6p-r6v2-jvc5
Warn: Project is vulnerable to: GHSA-765h-qjxv-5f44
Warn: Project is vulnerable to: GHSA-f2jv-r9rf-7988
Warn: Project is vulnerable to: GHSA-43f8-2h32-f4cj
Warn: Project is vulnerable to: GHSA-qqgx-2p2h-9c37
Warn: Project is vulnerable to: GHSA-2pr6-76vf-7546
Warn: Project is vulnerable to: GHSA-8j8c-7jfh-h6hx
Warn: Project is vulnerable to: GHSA-896r-f27r-55mw
Warn: Project is vulnerable to: GHSA-jg8v-48h5-wgxg
Warn: Project is vulnerable to: GHSA-36fh-84j7-cv5h
Warn: Project is vulnerable to: GHSA-6c8f-qphg-qjgp
Warn: Project is vulnerable to: GHSA-jf85-cpcp-j695
Warn: Project is vulnerable to: GHSA-p6mc-m468-83gw
Warn: Project is vulnerable to: GHSA-29mw-wpgm-hmr9
Warn: Project is vulnerable to: GHSA-35jh-r3h4-6jhm
Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
Warn: Project is vulnerable to: GHSA-f8q6-p94x-37v3
Warn: Project is vulnerable to: GHSA-vh95-rmgr-6w4m
Warn: Project is vulnerable to: GHSA-xvch-5gv4-984h
Warn: Project is vulnerable to: GHSA-fhjf-83wg-r2j9
Warn: Project is vulnerable to: GHSA-hj48-42vr-x3v9
Warn: Project is vulnerable to: GHSA-g6ww-v8xp-vmwg
Warn: Project is vulnerable to: GHSA-hrpp-h998-j3pp
Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6
Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
Warn: Project is vulnerable to: GHSA-4g88-fppr-53pp
Warn: Project is vulnerable to: GHSA-4jqc-8m5r-9rpr
Warn: Project is vulnerable to: GHSA-4rq4-32rv-6wp6
Warn: Project is vulnerable to: GHSA-64g7-mvw6-v9qj
Warn: Project is vulnerable to: GHSA-3jfq-g458-7qm9
Warn: Project is vulnerable to: GHSA-r628-mhmh-qjhw
Warn: Project is vulnerable to: GHSA-9r2w-394v-53qc
Warn: Project is vulnerable to: GHSA-5955-9wpr-37jh
Warn: Project is vulnerable to: GHSA-qq89-hq3f-393p
Warn: Project is vulnerable to: GHSA-f5x3-32g6-xq36
Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
Warn: Project is vulnerable to: GHSA-cf4h-3jhx-xvhq
Warn: Project is vulnerable to: GHSA-v2p6-4mp7-3r9v
Warn: Project is vulnerable to: GHSA-776f-qx25-q3cc
Warn: Project is vulnerable to: GHSA-c4w7-xm78-47vh
Warn: Project is vulnerable to: GHSA-p9pc-299p-vxgp

Score

1.7

/10

Last Scanned on 2025-01-20

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More