
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
@coralogix/esbuild-plugin-node
Advanced tools
Metapackage which bundles opentelemetry node core and contrib instrumentations via an esbuild plugin
This is a fork of the awesome @opentelemetry/esbuild-plugin-node created by drewcorlin1.
This module provides a way to auto instrument any Node application to capture telemetry from a number of popular libraries and frameworks, via an esbuild plugin. You can export the telemetry data in a variety of formats. Exporters, samplers, and more can be configured via environment variables. The net result is the ability to gather telemetry data from a Node application without any code changes.
This module also provides a simple way to manually initialize multiple Node instrumentations for use with the OpenTelemetry SDK.
Compatible with OpenTelemetry JS API and SDK 1.0+
.
npm install --save @coralogix/esbuild-plugin-node
This module includes instrumentation for all supported instrumentations and all available data exporters. It provides a completely automatic, out-of-the-box experience. Please see the Supported Instrumentations section for more information.
Enable auto instrumentation by configuring it in your esbuild script:
const { openTelemetryPlugin } = require('@coralogix/esbuild-plugin-node');
const { build } = require('esbuild');
build({
entryPoints: ['src/server.ts'],
bundle: true,
outfile: 'dist/server.js',
target: 'node20',
platform: 'node',
sourcemap: true,
plugins: [openTelemetryPlugin()],
});
OpenTelemetry Meta Packages for Node automatically loads instrumentations for Node builtin modules and common packages.
Enable auto instrumentation by configuring it in your esbuild script:
const { openTelemetryPlugin } = require('@coralogix/esbuild-plugin-node');
const { build } = require('esbuild');
build({
entryPoints: ['src/server.ts'],
bundle: true,
outfile: 'dist/server.js',
target: 'node20',
platform: 'node',
sourcemap: true,
plugins: [openTelemetryPlugin()],
});
Custom configuration for each of the instrumentations can be passed to the plugin, by providing an object with the name of the instrumentation as a key, and its configuration as the value.
const { openTelemetryPlugin } = require('@coralogix/esbuild-plugin-node');
const { build } = require('esbuild');
build({
entryPoints: ['src/server.ts'],
bundle: true,
outfile: 'dist/server.js',
target: 'node20',
platform: 'node',
sourcemap: true,
plugins: [
openTelemetryPlugin({
instrumentationConfig: {
'@opentelemetry/instrumentation-aws-sdk': {
suppressInternalInstrumentation: true,
},
},
}),
],
});
This esbuild script will instrument non-builtin packages but will not configure the rest of the OpenTelemetry SDK to export traces from your application. To do that you must also configure the SDK.
The esbuild script currently only patches non-builtin modules (more specifically, modules in opentelemetry-js-contrib), so this is also the place to configure the instrumentation for builtins or add any additional instrumentations.
There are limitations to the configuration options for each package. Most notably, any functions (like ignoreIncomingRequestHook
in the example) are not allowed to be passed in to plugins.
The reason for this is that the current mechanism of instrumenting packages involves stringifying the instrumentation configs, which does not account for any external scoped dependencies, and thus creates subtle opportunities for bugs.
const {
getNodeAutoInstrumentations,
} = require('@opentelemetry/auto-instrumentations-node');
const {
AsyncHooksContextManager,
} = require('@opentelemetry/context-async-hooks');
const {
OTLPTraceExporter,
} = require('@opentelemetry/exporter-trace-otlp-http');
const { NodeSDK } = require('@coralogix/sdk-node');
const instrumentations = getNodeAutoInstrumentations();
const sdk = new NodeSDK({
traceExporter: new OTLPTraceExporter(),
contextManager: new AsyncHooksContextManager().enable(),
instrumentations,
});
sdk.start();
process.on('SIGTERM', () => {
sdk.shutdown().finally(() => process.exit(0));
});
See @opentelemetry/auto-instrumentations-node for the supported packages.
Note that Node.js builtin modules will not be patched by this plugin.
APACHE 2.0 - See LICENSE for more information.
FAQs
Metapackage which bundles opentelemetry node core and contrib instrumentations via an esbuild plugin
The npm package @coralogix/esbuild-plugin-node receives a total of 257 weekly downloads. As such, @coralogix/esbuild-plugin-node popularity was classified as not popular.
We found that @coralogix/esbuild-plugin-node 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 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.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.