npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

vitalsigns-mongodb

v1.0.2

Published

MongoDB monitor for vitalsigns

Downloads

7

Readme

vitalsigns-mongodb

MongoDB monitor for vitalsigns

Runs db.stats() against a mongodb database

Installation

In your project folder, type:

npm i vitalsigns
npm i vitalsigns-mongodb

Basic Usage

Load up VitalSigns and add a mongodb monitor:

var VitalSigns = require('vitalsigns'),
	vitals = new VitalSigns();

// using monk
var monk = require('monk');
vitals.monitor('vitalsigns-mongodb', {db: monk('localhost/test')});

// using node-mongodb-native
var mongodb = require('mongodb');
var MongoClient = mongodb.MongoClient;

// Use connect method to connect to the Server
MongoClient.connect('mongodb://localhost/test', function(err, db) {
	vitals.monitor('vitalsigns-mongodb', {db: db});
});

We need to know when we go unhealthy...

vitals.unhealthyWhen('vitalsigns-mongodb', 'ok').not.equals(1);

Identifying the issue

var report = vitals.getReport();
console.log(report['vitalsigns-mongodb'].err);

Monitoring multiple databases

Vitalsigns supports custom names for monitors so you can monitor multiple databases by giving unique names

vitals.monitor('vitalsigns-mongodb', {db: monk('localhost/app'), name: 'app_db'});
vitals.monitor('vitalsigns-mongodb', {db: monk('localhost/secret', name: 'secret_db')});

We need to know when we go unhealthy...

vitals.unhealthyWhen('app_db', 'ok').not.equals(1);

Sample report

Single database

{
	'vitalsigns-mongodb': {
		db: 'test',
		collections: 8,
		objects: 28,
		avgObjSize: 361.14285714285717,
		dataSize: 10112,
		storageSize: 29278208,
		numExtents: 15,
		indexes: 6,
		indexSize: 49056,
		fileSize: 67108864,
		nsSizeMB: 16,
		extentFreeList: { num: 0, totalSize: 0 },
		dataFileVersion: { major: 4, minor: 22 },
		ok: 1
	},
	healthy: true
}

Multiple databases

{
	'app_db': {
		db: 'test',
		collections: 8,
		objects: 28,
		avgObjSize: 361.14285714285717,
		dataSize: 10112,
		storageSize: 29278208,
		numExtents: 15,
		indexes: 6,
		indexSize: 49056,
		fileSize: 67108864,
		nsSizeMB: 16,
		extentFreeList: { num: 0, totalSize: 0 },
		dataFileVersion: { major: 4, minor: 22 },
		ok: 1
	},
	'secret_db': {
		ok: 0,
		err: { errmsg: '[Error: failed to connect to [localhost:27016]]' }
	},
	healthy: true
}

Options

  • db: Monk or Mongodb database instance
  • freq: Check frequency