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 🙏

© 2025 – Pkg Stats / Ryan Hefner

nagios-parser-docker

v3.0.1

Published

Nagios parser AI

Downloads

3

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

rogierslagrogierslag

Keywords

Readme

Magnet.me

nagios-parser-docker-api

In order to read the status of our nagios servers, we use the following service, which runs within docker. It exposes the status of nagios through HTTP in a sensible way

Endpoints

| Endpoint | Filters | Description | |---|---|---| | / | No | Returns the entire overview of Nagios | | /info | No | Returns the information about Nagios | | /program | No | Returns the informatino about running Nagios program and settings | | /hosts/:host/services/:service | Yes | Returns service information about the specified service on the specified host | | /hosts/:host/services | Yes | Returns service information about services on the specified host | | /hosts/:host | No | Returns host information on the specified host | | /hosts | Yes | Returns host information on all hosts | | /services/:service | Yes | Returns service information about services with the specified service name | | /services | Yes | Returns service information on all services | | /contacts | No | Returns all contact information |

Websockets

You can also enable --with-ws as a command line flag. The service will start with a websockets endpoint at /. This will send you either update-hosts or update-services if their state changed significantly.

Notifications will be sent for the following changes:

  • New services or hosts added,
  • Services or hosts were removed,
  • A host or services state changed,
  • A host or service state changed (HARD/SOFT),
  • Notifications will be surpressed for flapping hosts and services.

CORS

For easier integration (as you should only expose this data on your internal network), you can accept all Origins for CORS. Pass the flag --allow-all-cors for this to the script.

Filters

| Filter | Values | Description | |---|---|---| | state | OK, WARNING, CRITICAL, UNKNOWN | Only show services or hosts which match the speficied state. Prepend with ! for a negation. So !OK will return all non-OK services or hosts | | flapping | true, false, 1, 0 | Only show services or hosts which are currently flapping (or not) |

Running it

Docker Automated build npm

You can start it as follows docker run -v /var/cache/nagios3/:/opt/nagios -p 8080:8080 magnetme/nagios-parser-docker-api:latest. In this case you can just execute http://localhost:8080 to see all of nagios' data in JSON format.