Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/lumigo-io/lumigo-node
Lumigo's Node.js Distributed Tracing and Performance Agent
https://github.com/lumigo-io/lumigo-node
debugging distributed-tracing instrumentation lumigo monitoring node serverless tracer
Last synced: about 1 month ago
JSON representation
Lumigo's Node.js Distributed Tracing and Performance Agent
- Host: GitHub
- URL: https://github.com/lumigo-io/lumigo-node
- Owner: lumigo-io
- License: apache-2.0
- Created: 2019-05-08T05:03:19.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2024-04-17T15:24:47.000Z (5 months ago)
- Last Synced: 2024-04-19T21:13:54.846Z (5 months ago)
- Topics: debugging, distributed-tracing, instrumentation, lumigo, monitoring, node, serverless, tracer
- Language: JavaScript
- Homepage: https://lumigo.io
- Size: 4.92 MB
- Stars: 74
- Watchers: 9
- Forks: 13
- Open Issues: 8
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
- awesome-layers - Lumigo Node Layer - node-tracer](https://api.globadge.com/v1/badgen/aws/lambda/layer/latest-version/us-east-1/114300393969/lumigo-node-tracer) | (Layers / Monitoring)
README
# lumigo-node :stars:
[](https://dl.circleci.com/status-badge/redirect/gh/lumigo-io/lumigo-node/tree/master)
[](https://codecov.io/gh/lumigo-io/lumigo-node)
[](https://badge.fury.io/js/%40lumigo%2Ftracer)
[](https://opensource.org/licenses/Apache-2.0)
[](https://github.com/semantic-release/semantic-release)
This is [`@lumigo/tracer`](https://), Lumigo's Node.js agent for distributed tracing and performance monitoring.
Supported NodeJS runtimes: 12.x, 14.x, 16.x, and 18.x
## Usage
The `@lumigo/tracer` package allows you to pursue automated metric gathering through Lambda Layers, automated metric gathering and instrumentation through the Serverless framework, or manual metric creation and implementation.
### With Lambda Layers
* When configuring your Lambda functions, include the appropriate Lambda Layer ARN [from these tables](https://github.com/lumigo-io/lumigo-node/blob/master/layers)
*Note* - Lambda Layers are an optional feature. If you decide to use this capability, the list of Lambda layers available is available [here.](https://github.com/lumigo-io/lumigo-node/blob/master/layers)
### With Serverless framework
* To configure the Serverless Framework to work with Lumigo, simply install our plugin: [**serverless-lumigo-plugin**](https://github.com/lumigo-io/serverless-lumigo-plugin/blob/master/README.md)
### Manually
To manually configure Lumigo in your Lambda functions:
* First, install the `@lumigo/tracer` package using your preferred package manager:
```bash
$ npm i @lumigo/tracer
# or
$ yarn add @lumigo/tracer
```
* Next, wrap your `handler` in Lumigo's `trace` function (note: replace `YOUR-TOKEN-HERE` with your Lumigo API token):
```javascript
// javascript
const lumigo = require('@lumigo/tracer')({ token: 'YOUR-TOKEN-HERE' })
const myHandler = async (event, context, callback) => { ... }
exports.handler = lumigo.trace(myHandler)
```
```typescript
// typescript
import lumigo from '@lumigo/tracer';
const tracer = lumigo({ token: 'YOUR-TOKEN-HERE' });
export const handler = tracer.trace(async (event, context) => {
...
});
```
#### Note
For Typescript users, you must add the following to your `tsconfig.json` file:
```json
{
...,
"esModuleInterop": true,
}
```
You can read more about it [here](https://www.typescriptlang.org/tsconfig#esModuleInterop)
* Your function is now fully instrumented
## Configuration
`@lumigo/tracer` 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 keys that match the supplied regular expressions. All regular expressions are case-insensitive. By default, Lumigo applies the following regular expressions: `[".*pass.*", ".*key.*", ".*secret.*", ".*credential.*", ".*passphrase.*"]`.
* We support more granular masking using the following parameters. If not given, the above configuration is the fallback: `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`.
* `LUMIGO_SECRET_MASKING_EXACT_PATH='["key1.key2", "key3.key4"]'` - Prevents Lumigo from sending keys that match the supplied path (we support nested fields). All paths are case-insensitive.
* `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.
* `LUMIGO_PROPAGATE_W3C=TRUE` - Add W3C TraceContext headers to outgoing HTTP requests. This enables uninterrupted transactions with applications traced with OpenTelemetry.
* `LUMIGO_SWITCH_OFF=TRUE` - In the event a critical issue arises, this turns off all actions that Lumigo takes in response to your code. This happens without a deployment, and is picked up on the next function run once the environment variable is present.
* `LUMIGO_AUTO_TAG=key1.key2,key3` - Configure execution tags that will be driven directly from the event for the supplied key (we support nested fields).
### Step Functions
If your function is part of a set of step functions, you can add the flag `step_function: true` to the Lumigo tracer import. Alternatively, you can configure the step function using an environment variable `LUMIGO_STEP_FUNCTION=True`. When this is active, Lumigo tracks all states in the step function in a single transaction, easing debugging and observability.
```javascript
const lumigo = require('@lumigo/tracer')({ token: 'DEADBEEF', step_function: true })
```
Note: the tracer adds the key `"_lumigo"` to the return value of the function.
If you override the `"Parameters"` configuration, add `"_lumigo.$": "$._lumigo"` to ensure this value is still present.
Below is an example configuration for a Lambda function that is part of a step function that has overridden its parameters:
```json
"States": {
"state1": {
"Type": "Task",
"Resource": "arn:aws:lambda:us-west-2:ACCOUNT:function:FUNCTION_NAME",
"Parameters": {
"Changed": "parameters",
"_lumigo.$": "$._lumigo"
},
"Next": "state2"
},
"state2": {
"Type": "pass",
"End": true
}
}
```
## Logging Programmatic Errors
With the tracer configured, simply call
```javascript
console.log("[LUMIGO_LOG] ");
```
to create custom errors that are visible throughout the platform. This can be used anywhere in your Lambda code, and is included with the `@lumigo/tracer` package.
## Adding Execution Tags
You can add execution tags to a function with dynamic values using the parameter `addExecutionTag`.
These tags will be searchable from within the Lumigo platform.
### Adding tags for Manual tracing
To add a tag to a manual trace statement:
* Add the following to your code:
```javascript
const lumigo = require('@lumigo/tracer')({ token: 'YOUR-TOKEN-HERE' })
```
* Add execution tags by using
```javascript
lumigo.addExecutionTag('', '');
```
### Adding tags for Auto tracing
To add a tag to an automatically-traced function:
* Add the following to the top of your handler's .js file:
```javascript
const lumigo = require('@lumigo/tracer')
```
* Use
```javascript
lumigo.addExecutionTag('', '');
```
anywhere in your lambda code.
### Execution Tag Limitations
Execution tags are subject to the following limitations:
* The maximum number of tags is 50.
* Key length must be between 1 and 50.
* Value length must be between 1 and 70.
### Scrubbing Limitations
Secrets scrubbing are subject to the following limitations:
* Only JSON data secrets scrubbing is supported