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-instrumentation-openwhisk

v0.2.1

Published

Zipkin Tracing Instrumentation Wrappers for OpenWhisk Actions and Client Library

Downloads

8

Readme

zipkin-instrumentation-openwhisk

This library enables Zipkin tracing support for serverless functions running on the OpenWhisk platform.

It supports instrumenting both the function handlers and the openwhisk client library.

install

npm install zipkin-instrumentation-openwhisk 

Using NPM modules on OpenWhisk requires the user to install them locally and include this node_modules directory in the deployment archive.

See here for more details.

Both the base zipkin module and a transport module (e.g. zipkin-transport-http ) must be included within this package.

usage - serverless functions

The instrumentation wraps the handler functions to record zipkin trace events for each invocation. Parent trace identifiers should be passed in using the _zipkin invocation property. These values are automatically added if you are wrapping the client library, see below.

const {Tracer, ExplicitContext, BatchRecorder} = require('zipkin');
const {HttpLogger} = require('zipkin-transport-http');
const wrap = require('zipkin-instrumentation-openwhisk');

const ctxImpl = new ExplicitContext()

const recorder = new BatchRecorder({
  logger: new HttpLogger({
    endpoint: 'http://your_trace_server_ip:9411/api/v1/spans'
  })
});

const tracer = new Tracer({ctxImpl, recorder});
const serviceName = 'greeting-service';

const handler = function (params) {
  const name = params.name || 'stranger';

  return {message: `Hello, ${name}!`};
}

exports.handler = wrap(handler, {tracer, serviceName});

usage - client library

The library will also wrap the OpenWhisk client library, allowing you to trace HTTP calls to the platform.

When the library is used to invoke other serverless functions, the parent trace identifiers are automatically added to the request.

const {Tracer, ExplicitContext, BatchRecorder} = require('zipkin');
const {HttpLogger} = require('zipkin-transport-http');
const wrap = require('zipkin-instrumentation-openwhisk');

const ctxImpl = new ExplicitContext()

const recorder = new BatchRecorder({
  logger: new HttpLogger({
    endpoint: 'http://your_trace_server_ip:9411/api/v1/spans'
  })
});

const tracer = new Tracer({ctxImpl, recorder});
const serviceName = 'greeting-service';

const openwhisk = require('openwhisk')
const ow = wrap(openwhisk(), { tracer, serviceName });

ow.actions.invoke({actionName: 'myServerlessFn'}).then(result => ...)

testing

Using the ConsoleRecorder module will log traces to the console, rather than the Zipkin server. This can help to understand what is being sent to the server.

const {Tracer, ExplicitContext, BatchRecorder, ConsoleRecorder} = require('zipkin')

const ctxImpl = new ExplicitContext()
const recorder = new ConsoleRecorder()

const tracer = new Tracer({ctxImpl, recorder})