zettajs/zetta-usage-addon

An addon to monitor data transfer between a hub and cloud

Zetta Usage Resource

API Driven analytics collection for the Z2Z protocol.

Install

npm install zetta-usage-addon --save

Usage

var zetta = require('zetta');
var MemDeviceRegistry = require('./memory_device_registry');
var MemPeerRegistry = require('./memory_peer_registry');
var UsageApp = require('zetta-usage-addon');

var options = {};

// Once hub is connected only send metrics every 30 seconds
//options.publishFrequency = 30000;
//options.publishHeaders  = true|falsey
//options.ignoredHeaders = []; Headers to stripout 
//options.enableApi = true|false. Usage api /usage

var app = new UsageApp(options)

zetta({registry: new MemDeviceRegistry(), peerRegistry: new MemPeerRegistry()})
  .name('server.1')
  .use(app.collect())
  .listen(1338);

zetta-usage-addon's Issues

Remove usage[connectionId] after peer disconnect.

No reason to keep that for the lifetime of the process. I think on _peer/disconnect we can remove it.

Crashes in some cases

 /zetta_target/node_modules/zetta-usage-addon/usage_app.js:41
 usage[connectionId].active = false;
 ^
 TypeError: Cannot set property 'active' of undefined
 at /zetta_target/node_modules/zetta-usage-addon/usage_app.js:41:34
 at EventEmitter.<anonymous> (/zetta_target/node_modules/zetta/lib/pubsub_service.js:65:5)
 at EventEmitter.emit (events.js:95:17)
 at PubSub.publish (/zetta_target/node_modules/zetta/lib/pubsub_service.js:11:16)
 at null.<anonymous> (/zetta_target/node_modules/zetta/lib/http_server.js:135:29)
 at emit (events.js:92:17)
 at Socket.<anonymous> (/zetta_target/node_modules/zetta/lib/peer_socket.js:113:10)
 at Socket.emit (events.js:117:20)
 at _stream_readable.js:929:16
 at process._tickDomainCallback (node.js:463:13)