# event-loop-monitor

> NodeJS event loop latency monitor

Latest version **0.2.0** (published 2016-05-23) · MIT license · 0 weekly downloads

## Install

```sh
npm install event-loop-monitor
pnpm add event-loop-monitor
yarn add event-loop-monitor
bun add event-loop-monitor
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support; pre 1.0.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 0.2.0 |
| Published | 2016-05-23 |
| First published | 2014-01-12 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 45 |
| Author | Kirill Borovikov |
| Maintainers | olegas |
| Keywords | eventloop, latency |

## Links

- npm: https://www.npmjs.com/package/event-loop-monitor
- Repository: https://github.com/Olegas/node-event-loop-monitor
- Homepage: https://github.com/Olegas/node-event-loop-monitor#readme
- Issues: https://github.com/Olegas/node-event-loop-monitor/issues
- npm.io page: https://npm.io/package/event-loop-monitor

## Alternatives

- [async-exit-hook](https://npm.io/package/async-exit-hook.md) — 3.7M weekly downloads
- [evnty](https://npm.io/package/evnty.md) — 7.2K weekly downloads
- [eleventy-plugin-asciidoc](https://npm.io/package/eleventy-plugin-asciidoc.md) — 3.5K weekly downloads
- [@jswork/next-get2get](https://npm.io/package/@jswork/next-get2get.md) — 945 weekly downloads
- [@dashersw/axon](https://npm.io/package/@dashersw/axon.md) — 934 weekly downloads

## Recent versions

- 0.2.0 (latest) — 2016-05-23
- 0.1.0 — 2015-02-16
- 0.0.4 — 2015-01-09
- 0.0.3 — 2014-01-13
- 0.0.2 — 2014-01-13
- 0.0.1 — 2014-01-12

## README

node-event-loop-monitor
=======================

NodeJS event loop latency monitor

Installation
------------

```
npm install event-loop-monitor --save
```

Usage
-----

```javascript
var monitor = require('event-loop-monitor');

// data event will fire every 4 seconds
monitor.on('data', function(latency) {
  console.log(latency); // { p50: 1026, p90: 1059, p95: 1076, p99: 1110, p100: 1260 }   
});

monitor.resume(); // to start measuring

// later...
monitor.stop(); // to stop measuring
```

What does it mean?
------------------

In example above this means that in last 4 seconds 50% of events is "late" by 1025 microseconds (1.025ms), 90% is late by 1059 microseconds (1.059ms) and so on.

CHANGELOG
--------

### 0.1.0

Removed `.unref()` from scanning interval. From now on, module will hold process running, until `.stop()` is called.

---
_Source: https://npm.io/package/event-loop-monitor · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._
