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

@risingstack/jaeger

v2.5.0

Published

Out of the box OpenTracing instrumentation for Node.js and Jaeger

Downloads

11

Readme

jaeger-node

Build Status

Out of the box distributed tracing for Node.js applications.

WARNING: experimental library, do not use in production yet

This library is a higher level wrapper around opentracing-auto, that you should consider to use instead of this library.

Technologies

Requirements

  • Node.js, >= v8
  • Jaeger

Getting started

npm install @risingstack/jaeger
// must be in the first two lines of your application
const Tracer = require('@risingstack/jaeger')
const tracer = new Tracer({
  serviceName: 'my-server-2'
})

// rest of your code
const express = require('express')
// ...

To start Jaeger and visit it's dashboard:

docker run -d -p5775:5775/udp -p6831:6831/udp -p6832:6832/udp -p5778:5778 -p16686:16686 -p14268:14268 jaegertracing/all-in-one:latest && open http://localhost:16686

Example

The example require a running MongoDB.

npm run example
curl http://localhost:3000
open http://localhost:16686

Jaeger Node.js tracing

API

new Tracer(args)

Create a new Tracer and instrument modules.

  • args.serviceName: Name of your service
    • required
    • example: 'my-service-1'
  • args.sampler: Jaeger sampler, see sampler docs
    • optional
    • default: new jaeger.RateLimitingSampler(1)
  • args.reporter: Jaeger reporter, see reporter docs
    • optional
    • default: new jaeger.RemoteReporter(new UDPSender())
  • args.options: Jaeger options, see docs
    • optional
    • example: { tags: { gitHash: 'foobar' } }

Instrumentations

Check out opentracing-auto instrumentations.

EMSGSIZE and UDP buffer limits

Read more about it in the Client Libraries documentation.