Registry / devops / node-red-contrib-msg-speed

node-red-contrib-msg-speed

JSON →
library2.1.0jsnpmunverified

A Node-RED node (v2.1.0) that measures the rate at which messages arrive using a moving window. It counts messages over a configurable interval (seconds, minutes, or hours) and outputs speed stats every second. Supports topic-dependent statistics and message chaining for performance. Ideal for monitoring flow throughput. Maintained by bartbutenaers with regular updates.

npm install node-red-contrib-msg-speed
INSTALL
IMPORT
SIG · NODE-RED-CONTRIB-M
N
node-red-contrib-msg-speed
devopsjavascriptv2.1.0
harness data pending
Install & Compatibility
Where this runs

No compatibility data collected yet for this library.

Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

node-red-contrib-msg-speed
Install via npm: npm install node-red-contrib-msg-speed (in ~/.node-red)
Global install: npm install -g node-red-contrib-msg-speed
Must be installed inside the Node-RED user directory (~/.node-red) for proper discovery.

Shows how to install and configure the msg-speed node in Node-RED to measure message rate with a moving window.

// This node is used via the Node-RED editor, not programmatically. // After installation, add a 'msg-speed' node from the palette. // Configure the interval (e.g., 5) and frequency (e.g., 'sec') in the node's settings. // Connect input messages; the node outputs speed stats to the first output and passes the original message to the second output. // Example flow JSON can be found in the package's examples. // See https://github.com/bartbutenaers/node-red-contrib-msg-speed for details.
Debug
Known issues
breakingIn versions < 0.0.5, message chaining was done via parallel wires, causing cloning overhead. Upgrade to 0.0.5+ for performance via second output.
fix
Update to latest version: npm install node-red-contrib-msg-speed@latest in ~/.node-red
affects: <0.0.5
gotchaThe node outputs speed every second based on a moving window; intermediate messages are not output until the next tick.
fix
Design flows assuming one output per second, not per message.
affects: >=0.0.5
gotchaTopic-dependent statistics require enabling the option in node config; otherwise msg.topic is not set.
fix
Enable 'topic dependent statistics' in node properties to get per-topic speed.
affects: >=1.0.0
deprecatedThe msg.topic field for aggregated statistics uses value 'all_topics'; this may change in future.
fix
Check for 'all_topics' string; adapt if upstream changes.
affects: >=1.0.0
Errors
Common errors & fixes
Error: Cannot find module 'node-red-contrib-msg-speed'
Module installed globally instead of in Node-RED user directory.
fix
Run: cd ~/.node-red && npm install node-red-contrib-msg-speed
TypeError: Cannot read property 'frequency' of undefined
Accessing msg.frequency in a node that is not the msg-speed output.
fix
Ensure you are reading from the first output of the msg-speed node.
Node not found in palette
Node-RED not restarted after install, or installed wrong directory.
fix
Restart Node-RED; verify install in ~/.node-red/node_modules
Upgrade
Version history
2.1.0latest on npm
Audit
Dependencies
node-redoptionalRuntime dependency for Node-RED nodes
Agent activity
2 hits · last 30 days
node
2
Resources
node-red-contrib-msg-speed — npm install node-red-contrib-msg-speed · libregistry