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

zipkin-javascript-opentracing

v3.0.0

Published

An opentracing implementation for zipkin

Downloads

7,758

Readme

Zipkin-Javascript-Opentracing Build Status Coverage Status

Installation

Run npm install --save zipkin-javascript-opentracing to install the library.

For usage instructions, please see the examples in the examples/ directory. There is a basic vanilly javascript example that shows how to use the tracer in the context of a single express server and there is an advanced vanilla javascript example that shows how multiple services (express API and frontend) might interact and share a tracing context.

Limitations

injecting and ejecting

We currently only support HTTP Headers. If you need your own mechanism, feel free to do a PR. Also we assume that you only inject the HTTP Headers once, otherwise we will send multiple ClientSend annotations for you.

Also you can only finish spans which were not extracted. If you like this behaviour to be different, please open an issue.

Flags

They are currently not supported, feel free to do a PR.

Follows From (zipkin)

FollowsFrom is not supported by openTracing, as far as I understand.

Additional options for starting a span

We need to know if this is a server or client to set the right annotations. Therefore we need the kind attribute to be set.

Example

All examples need to run zipkin on "localhost:9411". This is best achieved by using docker:

docker run -d -p 9411:9411 openzipkin/zipkin

Basic

To see how to use this library with only one service see examples/vanillajs/basic. You can run the example with npm run example:basic.

Advanced

In order to see how different services may pick up spans and extend them, please see the advanced example at examples/vaniallajs/advanced. You can run the example with npm run example:advanced.