nodejsagent provides a set of complementary instrumentation features for collecting relevant data to be processed by Hypertrace.
git submodule update --init --recursive
npm run generate_pb
npm run build
You can then install the generated .tgz as a normal dependency.
Note: Using npm link doesnt solve the local testing problem as it will use the hypertrace package dev-dependencies during instrumentation instead of the targetted node app
Run the example application
cd ./test/externalServices docker-compose up -d cd -
npm run test
cd ./test/externalServices docker-compose down cd -
Tests should be added to the
test directory, in a structure that matches that of the file you are attempting to test.
Ideally all functionality is testable in locally runnable unit-tests(as opposed to in a docker container), primarily for ease of debugging.
To build the layer & upload it to an AWS account:
./build_layer.sh <REGION>where region is the region you want the layer to be available in
HT_REPORTING_ENDPOINTto a valid OTLP collector address. - If using with a collector layer, no need to specify an OTLP address as it will export to localhost:4317
Hypertrace Node.js Agent
The npm package @hypertrace/nodejsagent receives a total of 235 weekly downloads. As such, @hypertrace/nodejsagent popularity was classified as not popular.
We found that @hypertrace/nodejsagent 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.
Did you know?
Socket installs a Github app to automatically flag issues on every pull request and report the health of your dependencies. Find out what is inside your node modules and prevent malicious activity before you update the dependencies.