@dnlup/doc
Advanced tools
Get usage and health data about your Node.js process.
doc is a small module that helps you collect health metrics about your Node.js process.
It does that by using only the API available on Node itself (no native dependencies).
It doesn't have any ties with an APM platform, so you are free to use anything you want for that purpose.
Its API lets you access both computed and raw values, where possible.
doc([options])doc.Sampler
CpuMetric
ResourceUsageMetric
EventLoopDelayMetric
EventLoopUtilizationMetric
GCMetric
gcMetric.pause
GCEntry
GCAggregatedEntry
new GCAggregatedEntry()gcAggregatedEntry.flagsgcAggregatedEntry.flags.nogcAggregatedEntry.flags.constructRetainedgcAggregatedEntry.flags.forcedgcAggregatedEntry.flags.synchronousPhantomProcessinggcAggregatedEntry.flags.allAvailableGarbagegcAggregatedEntry.flags.allExternalMemorygcAggregatedEntry.flags.scheduleIdledoc.eventLoopUtilizationSupporteddoc.resourceUsageSupporteddoc.gcFlagsSupported$ npm i @dnlup/doc
$ npm i @dnlup/doc@next
You can import the module by using either CommonJS or ESM.
By default doc returns a Sampler instance that collects metrics about cpu, memory usage, event loop delay and event loop utilization (only on Node versions that support it).
const doc = require('@dnlup/doc')
const sampler = doc() // Use the default options
sampler.on('sample', () => {
doStuffWithCpuUsage(sampler.cpu.usage)
doStuffWithMemoryUsage(sampler.memory)
doStuffWithEventLoopDelay(sampler.eventLoopDelay.computed)
doStuffWithEventLoopUtilization(sampler.eventLoopUtilization.utilization) // Available only on Node versions that support it
})
import doc from '@dnlup/doc'
const sampler = doc()
sampler.on('sample', () => {
doStuffWithCpuUsage(sampler.cpu.usage)
doStuffWithMemoryUsage(sampler.memory)
doStuffWithEventLoopDelay(sampler.eventLoopDelay.computed)
doStuffWithEventLoopUtilization(sampler.eventLoopUtilization.utilization) // Available only on Node versions that support it
})
A Sampler holds a snapshot of the metrics taken at the specified sample interval.
This behavior makes the instance stateful. On every tick, a new snapshot will overwrite the previous one.
You can disable the metrics that you don't need.
const doc = require('@dnlup/doc')
// Collect only the event loop delay
const sampler = doc({ collect: { cpu: false, memory: false } })
sampler.on('sample', () => {
// `sampler.cpu` will be `undefined`
// `sampler.memory` will be `undefined`
doStuffWithEventLoopDelay(sampler.eventLoopDelay.computed)
doStuffWithEventLoopUtilization(sampler.eventLoopUtilization.utilization) // Available only on Node versions that support it
})
You can enable more metrics if you need them.
const doc = require('@dnlup/doc')
const sampler = doc({ collect: { gc: true } })
sampler.on('sample', () => {
doStuffWithCpuUsage(sampler.cpu.usage)
doStuffWithMemoryUsage(sampler.memory)
doStuffWithEventLoopDelay(sampler.eventLoopDelay.computed)
doStuffWithEventLoopUtilization(sampler.eventLoopUtilization.utilization) // Available only on Node versions that support it
doStuffWithGarbageCollectionDuration(sampler.gc.pause)
})
const doc = require('@dnlup/doc')
const sampler = doc({ collect: { activeHandles: true } })
sampler.on('sample', () => {
doStuffWithCpuUsage(sampler.cpu.usage)
doStuffWithMemoryUsage(sampler.memory)
doStuffWithEventLoopDelay(sampler.eventLoopDelay.computed)
doStuffWithEventLoopUtilization(sampler.eventLoopUtilization.utilization) // Available only on Node versions that support it
doStuffWithActiveHandles(sampler.activeHandles)
})
You can find more examples in the examples folder.
doc([options])It creates a metrics Sampler instance with the given options.
doc.SamplerEventEmitter.Metrics sampler.
It collects the selected metrics at a regular interval. A Sampler instance is stateful so, on each tick,
only the values of the last sample are available. Each time the sampler emits the sample event, it will overwrite the previous one.
doc.Sampler([options])options <Object>
sampleInterval <number>: sample interval (ms) to get a sample. On each sampleInterval ms a sample event is emitted. Default: 500 on Node < 11.10.0, 1000 otherwise. Under the hood the package uses monitorEventLoopDelay when available to track the event loop delay and this allows to increase the default sampleInterval.autoStart <boolean>: start automatically to collect metrics. Default: true.unref <boolean>: unref the timer used to schedule the sampling interval. Default: true.gcOptions <Object>: Garbage collection options
aggregate <boolean>: Track and aggregate statistics about each garbage collection operation (see https://nodejs.org/docs/latest-v12.x/api/perf_hooks.html#perf_hooks_performanceentry_kind). Default: falseflags <boolean>: , Track statistics about the flags of each (aggregated) garbage collection operation (see https://nodejs.org/docs/latest-v12.x/api/perf_hooks.html#perf_hooks_performanceentry_flags). aggregate has to be true to enable this option. Default: true on Node version 12.17.0 and newer.eventLoopDelayOptions <Object>: Options to setup monitorEventLoopDelay. Default: { resolution: 10 }collect <Object>: enable/disable the collection of specific metrics.
cpu <boolean>: enable cpu metric. Default: true.resourceUsage <boolean>: enable resourceUsage metric. Default: false.eventLoopDelay <boolean>: enable eventLoopDelay metric. Default: true.eventLoopUtilization <boolean>: enable eventLoopUtilization metric. Default: true on Node version 12.19.0 and newer.memory <boolean>: enable memory metric. Default: true.gc <boolean>: enable garbage collection metric. Default: false.activeHandles <boolean>: enable active handles collection metric. Default: false.If options.collect.resourceUsage is set to true, options.collect.cpu will be set to false because the cpu metric is already available in the resource usage metric.
sample'Emitted every sampleInterval, it signals that new data the sampler has collected new data.
sampler.start()Start collecting metrics.
sampler.stop()Stop collecting metrics.
sampler.cpuResource usage metric instance.
sampler.resourceUsageResource usage metric instance.
sampler.eventLoopDelayEvent loop delay metric instance.
sampler.eventLoopUtilizationEvent loop utilization metric instance.
sampler.gcGarbage collector metric instance.
sampler.activeHandles<number>Number of active handles returned by process._getActiveHandles().
sampler.memory<object>Object returned by process.memoryUsage().
CpuMetricIt exposes both computed and raw values of the cpu usage.
cpuMetric.usage<number>Cpu usage in percentage.
cpuMetric.raw<object>Raw value returned by process.cpuUsage().
ResourceUsageMetricIt exposes both computed and raw values of the process resource usage.
resourceUsage.cpu<number>Cpu usage in percentage.
resourceUsage.raw<object>Raw value returned by process.resourceUsage().
EventLoopDelayMetricIt exposes both computed and raw values about the event loop delay.
eventLoopDelay.computed<number>Event loop delay in milliseconds. On Node versions that support monitorEventLoopDelay, it computes this value using the mean of the Histogram instance. Otherwise, it uses a simple timer to calculate it.
eventLoopDelay.raw<Histogram> | <number>On Node versions that support monitorEventLoopDelay this exposes the Histogram instance. Otherwise, it exposes the raw delay value in nanoseconds.
eventLoopDelay.compute(raw)raw <number> The raw value obtained using the Histogram API.<number> The computed delay value.This function works only on node versions that support monitorEventLoopDelay. It allows to get computed values of the event loop delay from statistics other than the mean of the Histogram instance.
EventLoopUtilizationMetricIt exposes statistics about the event loop utilization.
eventLoopUtilization.idle<number>The idle value in the object returned by performance.eventLoopUtilization() during the sampleInterval window.
eventLoopUtilization.active<number>The active value in the object returned by performance.eventLoopUtilization() during the sampleInterval window.
eventLoopUtilization.utilization<number>The utilization value in the object returned by performance.eventLoopUtilization() during the sampleInterval window.
eventLoopUtilization.raw<object>Raw value returned by performance.eventLoopUtilization() during the sampleInterval window.
GCMetricIt exposes the garbage collector activity statistics in the specified sampleInterval using hdr histograms.
new GCMetric(options)options <object>: Configuration options
aggregate <boolean>: See gcOptions.aggregate in the Sampler options.flags <boolean>: See gcOptions.flags in the Sampler options.gcMetric.pauseIt tracks the global activity of the garbage collector.
gcMetric.majorThe activity of the operation of type major. It's present only if GCMEtric has been created with the option aggregate equal to true.
gcMetric.minorThe activity of the operation of type minor. It's present only if GCMEtric has been created with the option aggregate equal to true.
gcMetric.incrementalThe activity of the operation of type incremental. It's present only if GCMEtric has been created with the option aggregate equal to true.
gcMetric.weakCbThe activity of the operation of type weakCb. It's present only if GCMEtric has been created with the option aggregate equal to true.
GCEntryIt contains garbage collection data, represented with an hdr histogram. All timing values are expressed in nanoseconds.
new GCEntry()The initialization doesn't require options. It is created internally by a GCMEtric.
gcEntry.totalDuration<number>It is the total time of the entry in nanoseconds.
gcEntry.totalCount<number>It is the total number of operations counted.
gcEntry.mean<number>It is the mean value of the entry in nanoseconds.
gcEntry.max<number>It is the maximum value of the entry in nanoseconds.
gcEntry.min<number>It is the minimum value of the entry in nanoseconds.
gcEntry.stdDeviation<number>It is the standard deviation of the entry in nanoseconds.
gcEntry.summary<object>The hdr histogram summary. See https://github.com/HdrHistogram/HdrHistogramJS#record-values-and-retrieve-metrics.
gcEntry.getPercentile(percentile)percentile <number>: Get a percentile from the histogram.<number> The percentileSee https://github.com/HdrHistogram/HdrHistogramJS#record-values-and-retrieve-metrics.
GCAggregatedEntryIt extends GCEntry and contains garbage collection data plus the flags associated with it (see https://nodejs.org/docs/latest-v12.x/api/perf_hooks.html#perf_hooks_performanceentry_flags).
new GCAggregatedEntry()The initialization doesn't require options. It is created internally by a GCMEtric.
gcAggregatedEntry.flags<object>This object contains the various hdr histograms of each flag.
gcAggregatedEntry.flags.nogcAggregatedEntry.flags.constructRetainedgcAggregatedEntry.flags.forcedgcAggregatedEntry.flags.synchronousPhantomProcessinggcAggregatedEntry.flags.allAvailableGarbagegcAggregatedEntry.flags.allExternalMemorygcAggregatedEntry.flags.scheduleIdledoc.eventLoopUtilizationSupported<boolean>It tells if the Node.js version in use supports the eventLoopUtilization metric.
doc.resourceUsageSupported<boolean>It tells if the Node.js version in use supports the resourceUsage metric.
doc.gcFlagsSupported<boolean>It tells if the Node.js version in use supports GC flags.
FAQs
Get usage and health data about your Node.js process
The npm package @dnlup/doc receives a total of 280 weekly downloads. As such, @dnlup/doc popularity was classified as not popular.
We found that @dnlup/doc 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.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.
Security News
Research
Socket researchers found a malicious Maven package impersonating the legitimate ‘XZ for Java’ library, introducing a backdoor for remote code execution.