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

nemo-monitoring-module

v0.0.1

Published

All nessesary monitoring, service discovery, tracing, ... features in the NEMO project

Downloads

1

Readme

NEMO Monitoring Module

The NEMO monitoring-module contains all the nessesary tools for monitoring a microservice inside the NEMO environment.

Install

Go into the ./ root of your service and do:

mkdir modules cd modules git clone [email protected]:NEMO_BRiDGE/nemo-monitoring-module.git npm install

Update

cd modules/nemo-monitoring-module git pull origin master

How-To

Include

The init function expects the service name but defaults to environment variable NEMO_SVC_NAME if not set. It also expects the environment variable NODE_ENV but defaults to 'development' if not set.

var nemoMonitor = require('./modules/nemo-monitoring-module')('myService');

Tools

Currently there is only one tool integrated in monitoring.

Trace by Rising Stack

Trace keeps track of the communication flow inside of nemo and between the microservices. It can be configured in more detail using the trace specific config file in nemo-monitoring-module/src/trace.config.js. E.g. for the following settings:

  • apiKey: 'the api key for the current envidonment' // setting the key for the current environment at trace server
  • ignoreHeaders: {'user-agent': ['007']} // to exclude internal e.g. monitoring calls from the logs
  • collectorApiUrl: 'http://www.example.de/' // endpoint of the trace-server
  • other parameter: collectInterval, collectorLanguage, collectorApiSampleEndpoint, collectorApiServiceEndpoint, collectorApiApmMetricsEndpoint, collectorApiRpmMetricsEndpoint collectorApiEdgeMetricsEndpoint, collectorApiIncomingEdgeMetricsEndpoint, collectorApiExternalEdgeMetricsEndpoint