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 🙏

© 2026 – Pkg Stats / Ryan Hefner

opsview-api

v0.1.3

Published

A library to access opsview functionality from nodejs scripts instead of interfacing to the REST API directly

Readme

Opsview NodeJS module

Introduction

The motivation of this module is to provide some of the basic functionality of Opsview V3 in a nodejs classes module, instead of making api rest calls directly with unirest or the like.

Since it's mainly an utility library for the greater project hubot-commands as used in our company, I'm only implementing what we need in a most demanded basis, which means that in the first release, only setting downtimes is working. For the next one, I'm trying to push the reload configuration functionality.

Full documentation is in the code, on how to use the classes and each method, what arguments are expected, what exceptions are thrown and what result objects are returned.

The code follows an asynchronous flow with Promises (from the Bluebird library).

Usage

To prevent having to write credentials on a code file, the library will search for credentials and the opsview server address in the following file: $HOME/.opsview_secret (In Windows it's %USERPROFILE% instead of %HOME% if it's a pre-Windows10 version). This file is a properties file with the following keys:

  • opsview.login.username
  • opsview.login.password
  • opsview.host

example:

opsview.login.username=username
opsview.login.password=password
opsview.host=http://www.monitoringserver.com/rest

If the file exists, then it is handled automatically by the library and you've only got to use it like so:

var Opsview = require('opsview-api');

var opsview = new Opsview(3); //Instances version 3

var from = new Date(2016,2,5,20,40);
var to = new Date(2016,2,5,20,59);
var comment = "NodeJS Opsview Library test";
var hostPattern = "backend.server%";
var servicePattern = "serviceName";

opsview.setDowntime(from,to,comment,hostPattern,servicePattern)
	.then(function(response){
		console.log("The downtime was set, yay!");
	})
	.catch(function(error){
		console.log(`Something terrible happened: ${error.message}`);
	});

The library was designed to support different versions of the API, even though only the V3 is likely to be implemented.

Merge requests are welcome.