
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
@debugr/sentry
Advanced tools
This LogHandler will forward errors to Sentry.
This plugin does not use the Sentry SDK, because it's incompatible with AsyncLocalStorage,
which Debugr makes heavy use of.
npm install --save @debugr/sentry
import { Logger, LogLevel } from '@debugr/core';
import { SentryHandler } from '@debugr/sentry';
const globalContext = {
applicationName: 'example',
};
const logger = new Logger(globalContext, [
new SentryHandler({
dsn: 'https://publickey@my.sentry.host/123',
}),
]);
logger.setContextProperty('jobName', 'sentryTest');
logger.error(new Error('App crashed!'));
The SentryHandler constructor accepts an optional options object as the first argument.
The available options are:
| Option | Type | Default | Description |
|---|---|---|---|
dsn | string | (none) | The Sentry DSN. If unspecified or empty, the handler will not do anything. |
breadcrumbThreshold | LogLevel | LogLevel.DEBUG | The minimum level for entries to be collected as breadcrumbs. |
captureThreshold | LogLevel | LogLevel.ERROR | The minimum level at which entries should be captured and sent to Sentry. A captured entry will send all breadcrumbs collected within the same task prior to the entry being captured. |
captureProbability | number | 1 | The probability, as a float in the range <0, 1>, with which captured entries will be actually sent to Sentry. For example a value of 0.1 means 10% probability, so roughly 1 in every 10 captured entries will be sent. |
captureWholeTasks | boolean | true | Whether to wait for a task to finish before sending captured entries to Sentry. If this is set to true (the default), only the last entry captured within a task will be sent, with all prior captured entries from the same task included in the breadcrumbs. When set to false, each entry captured within a task will be sent immediately, including all prior breadcrumbs, which could result in multiple separate entries in Sentry when an error is logged multiple times. |
extractMessage | (entry: LogEntry) => string | (see description) | A callback which should extract a string message from a LogEntry. By default, if an error is part of the entry, its message is used; otherwise the entry message is used, if present; and finally a generic string is generated. |
levelMap | Record<number, string> | (none) | A map of custom log levels to Sentry log levels. Sentry recognises the following log levels: debug, info, warning, error and fatal. |
FAQs
Sentry log handler for Debugr
We found that @debugr/sentry demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers 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
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.