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

express-jaeger

v0.0.16

Published

A simple Express JS middleware to tracing requests wiht Jaeger Tracing.

Downloads

34

Readme

express-jaeger

A simple Jaeger middleware to tracing requests for your Express JS app.

Installation

$ npm i --save express-jaeger

Using it as a Middleware

Setup using Environment Variables

process.env.JAEGER_COLLECTOR_ENDPOINT = "http://192.168.0.1:14268/api/traces";
process.env.JAEGER_SERVICE_NAME = "express-jaeger-example";
process.env.JAEGER_AGENT_HOST = "192.168.0.1";
process.env.JAEGER_AGENT_PORT = "6831";

const { track } = require("express-jaeger");
const express = require("express");
const server = express();

server.use(track("/operationName1"));
server.use(track("/operationName2"));
server.use(track("/operationName3"));

server.get("/home", track("/home"), (req, res) => {
    res.status(200).send("Welcome!")
})

server.listen(3000);

Setup using Custom Objects

// TracingOptions

const options = {
  logger: {
    info: msg => {
      console.log("INFO ", msg);
    },
    error: msg => {
      console.log("ERROR", msg);
    }
  }
}

// TracingConfig

const config = {
  serviceName: "MyService",
  sampler: {
    type: "const",
    param: 1
  },
  reporter: {
    collectorEndpoint: "http://192.168.0.1:14268/api/traces",
    agentHost: "192.168.0.1",
    agentPort: "6831",
    logSpans: true
  }
};

const { track } = require("express-jaeger");
const express = require("express");
const server = express();

server.use(track("/operationName1", config, options));
server.use(track("/operationName2", config, options));
server.use(track("/operationName3", config, options));

server.get("/home", track("/home", config, options), (req, res) => {
    res.status(200).send("Welcome!")
})

server.listen(3000);

Running

Starting a Jaeger Server using Docker

$ docker run -d --name jaeger -e COLLECTOR_ZIPKIN_HTTP_PORT=9411 -p 5775:5775/udp -p 6831:6831/udp -p 6832:6832/udp -p 5778:5778 -p 16686:16686 -p 14268:14268 -p 9411:9411 jaegertracing/all-in-one:1.8

Once the Jaeger Server is active...

Starting your Express app

$ npm start

or

$ node /path/to/your/server.js

That's it

  1. Open your browser in http://localhost:3000/home
  2. In another tab, open http://localhost:16686 to see the Jaeger UI
  3. On the left menu select your service by the name ( process.env.JAEGER_SERVICE_NAME )
  4. Click on the Find Traces button and voilá.