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

seneca-zipkin-tracer

v0.2.0

Published

Seneca tracer sending data to zipkin

Downloads

8

Readme

Seneca

seneca-zipkin-tracer

npm version Build Status Coverage Status Dependency Status Gitter chat

  • Sponsor: nearForm
  • Node: 4.x, 6.x
  • Seneca: 3.3

This plugin sends traces about actions execution to a zipkin tracing system instance.

Both local and remote call are traced. Zipkin will receive the action pattern as the method name and the seneca tag as the serviceName.

If you're using this module, and need help, you can:

If you are new to Seneca in general, please take a look at senecajs.org. We have everything from tutorials to sample apps to help get you up and running quickly.

Install

npm install seneca-zipkin-tracer

Usage

You will need a running instance of zipkin (best way in dev is with docker).

Apart from that, usage is quite simple: just register the plugin and you're ready to trace.

var server = Seneca({tag: 'service-name'}).use('zipkin-tracer')

Location of zipkin can be configured through options:

var server = Seneca({tag: 'service-name'}).use('zipkin-tracer', {
  host: '127.0.0.1',
  port: 9411,
  url: '/api/v1/spans'
})

Assuming you have installed zipkin with the docker container linked above, you can reach the zipkin dashboard at http://localhost:9411/ where you should find all the traces collected for your service.

Options

The plugin accepts the same options of zipkin-simple:

  • host: location of zipkin server
  • port: port of the zipkin http transport
  • url: path where to send traces
  • transport: which transport to use (http, http-simple or custom function)
  • sampling: the sampling ratio, from 0 to 1 (0 means don't send data, 1 send all data)
  • for the http transport, batchSize and batchTimeout control the batching of spans and traces

Caveats

Currently only supports zipkin http transport

Test

To run tests locally,

npm run test

To obtain a coverage report,

npm run coverage; open docs/coverage.html

Contributing

The Senecajs org encourage open participation. If you feel you can help in any way, be it with documentation, examples, extra testing, or new features please get in touch.

License

Copyright (c) 2013 - 2016, Richard Rodger and other contributors. Licensed under MIT.