open-index/open-npm huggingface dataset:
npm package: @lumigo/lumigo-node-wrapper
Description: Lumigo wrapper to trace distributed architecture
Author: Orr Levinger
Latest version: 1.0.3
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# lumigo-node-wrapper
[![CircleCI](https://circleci.com/gh/lumigo-io/lumigo-node-wrapper/tree/master.svg?style=svg&circle-token=488f0e5cc37e20e9a85123a3afe3457a5efdcc55)](https://circleci.com/gh/lumigo-io/lumigo-node-wrapper/tree/master)

# WIP
npm package: @lumigo/microservices-node-tracer
Description: Lumigo wrapper to trace distributed architecture
Author: Orr Levinger
Latest version: 1.0.16
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @lumigo/microservices-node-tracer :stars:
[![CircleCI](https://circleci.com/gh/lumigo-io/lumigo-node-wrapper/tree/master.svg?style=svg&circle-token=488f0e5cc37e20e9a85123a3afe3457a5efdcc55)](https://circleci.com/gh/lumigo-io/lumigo-node-wrapper/tree/master)
[![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg)](https://github.com/semantic-release/semantic-release)


This is [`@lumigo/microservices-node-tracer`](https://), Lumigo's Node.js agent for microservices distributed tracing and performance monitoring.

Supported NodeJS runtimes: 12.x, 14.x

### Instrumenting Lumigo:

To configure Lumigo in your microservice:

* First, install the `@lumigo/microservices-node-tracer` package using your preferred package manager:

~~~bash
$ npm i @lumigo/microservices-node-tracer
~~~

### Instrumenting Lumigo programmatically:
* Import “lumigo_warpper” in the first row of the file (to avoid conflicts):

~~~js
// javascript
const lumigoWrapper = require("@lumigo/microservices-node-tracer");
~~~
* To initiate the tracing call the trace method (note: replace YOUR-TOKEN-HERE with your Lumigo API token). You can retrieve the token by going to Settings -> Tracing -> Manual tracing:

* Replace YOUR-SERVICE-NAME with some logical name (eg. todo-app)
~~~js
lumigoWrapper.trace(‘YOUR-TOKEN-HERE’,‘YOUR-SERVICE-NAME’);
~~~

### Instrumenting Lumigo as part of npm package.json start script:
~~~json
"scripts":{
"start": "export LUMIGO_TOKEN=‘YOUR-TOKEN-HERE’ && export LUMIGO_SERVICE_NAME=‘YOUR-SERVICE-NAME’ && node -r @lumigo/microservices-node-tracer app.js"
}
~~~
* Finally: Re-deploy your app.


## Configuration
`@lumigo/microservices-node-tracer` offers several different configuration options. Pass these to the microservice as environment variables:

* `LUMIGO_DEBUG=TRUE` - Enables debug logging
* `LUMIGO_SWITCH_OFF=TRUE` - In the event a critical issue arises, this turns off all actions that Lumigo takes in response to your code.
npm package: @lumigo/node-core
Description: Lumigo core node sdk
Author: Lumigo LTD
Latest version: 1.17.1

# node-core :stars:

[![CircleCI](https://circleci.com/gh/lumigo-io/lumigo-node.svg?style=svg&circle-token=47f40cb5e95e8532e73f69754fac65830b5e86a1)](https://circleci.com/gh/lumigo-io/lumigo-core)
[![codecov](https://codecov.io/gh/lumigo-io/lumigo-node/branch/master/graph/badge.svg?token=mUkKlI8ifC)](https://codecov.io/gh/lumigo-io/lumigo-core)
[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
[![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg)](https://github.com/semantic-release/semantic-release)

This is [`@lumigo/node-core`](https://github.com/lumigo-io/node-core), Lumigo's Node.js agent core tracing logic for distributed tracing and performance monitoring.
it is used by all our Node tracers to perform many of the shared logic across services

Supported NodeJS runtimes: 8.10, 10.x, 12.x, 14.x, 16.x, 18.x

## Configuration

`@lumigo/node-core` offers several different configuration options. Pass these to the Lambda function as environment variables:

* `LUMIGO_DEBUG=TRUE` - Enables debug logging
* `LUMIGO_SECRET_MASKING_REGEX='["regex1", "regex2"]'` - Prevents Lumigo from sending values for keys that match the supplied regular expressions. All regular expressions are case-insensitive. We support also more granular masking using `LUMIGO_SECRET_MASKING_REGEX_HTTP_REQUEST_BODIES`, `LUMIGO_SECRET_MASKING_REGEX_HTTP_REQUEST_HEADERS`, `LUMIGO_SECRET_MASKING_REGEX_HTTP_RESPONSE_BODIES`, `LUMIGO_SECRET_MASKING_REGEX_HTTP_RESPONSE_HEADERS`, `LUMIGO_SECRET_MASKING_REGEX_HTTP_QUERY_PARAMS` and `LUMIGO_SECRET_MASKING_REGEX_ENVIRONMENT`. By default, Lumigo applies the following regular expressions: `[".*pass.*", ".*key.*", ".*secret.*", ".*credential.*", ".*passphrase.*", ".*token.*"]`. The "magic" value `all` will prevent any value to be sent to Lumigo.
* `LUMIGO_DOMAINS_SCRUBBER='[".*secret.*"]'` - Prevents Lumigo from collecting both request and response details from a list of domains. This accepts a comma-separated list of regular expressions that is JSON-formatted. By default, the tracer uses `["secretsmanager\..*\.amazonaws\.com", "ssm\..*\.amazonaws\.com", "kms\..*\.amazonaws\.com"]`. **Note** - These defaults are overridden when you define a different list of regular expressions.

## Functionality

### Secret masking

Secrets scrubbing by list for regexes:

* support only json data secrets scrubbing