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

@cran/lib.node.telemetry

v0.0.3

Published

Telemetry node baseline integration

Downloads

6

Readme

Telemetry Baseline

CC BY-SA 4.0   NPM

Installation

npm install @cran/lib.node.telemetry

Basic Usage

Important: To properly utilize and configure instrumentation, this library must be imported and configured before all others, however it may be started at any time

NOTE: Do not combine auto and classic import methodologies from below, they are not compatible and will result in two reporters

import "@cran/lib.node.telemetry/auto";

-- or --

node --require @cran/lib.node.telemetry/auto [file.js]

Note: To see default tracing utilize the DEBUG environment variable

DEBUG=cran:telemetry:*,-cran:telemetry:fs

Advanced Usage

import { MetricTracer } from "@cran/lib.node.telemetry";

MetricTracer.init({
  prefix: "my_app_",
  trace ( span ) {
    // default utilizes debug
    console.log(span);
  },
  relabel: {
    "@opentelemetry/instrumentation-fs" ( ) {
      // turn off metric reporting
      return null;
    },
    "@opentelemetry/instrumentation-http" ( span ) {
      // alter labels (span.attributes is defaulted)
      return { ...span.attributes, my_label: "my_value" };
    },
  },
  instrumentations: [
    require("instrumentation-custom")(),
  ],
  override: {
    // SEE https://www.npmjs.com/package/@opentelemetry/auto-instrumentations-node?activeTab=readme
    "@opentelemetry/instrumentation-http": {
      applyCustomAttributesOnSpan ( span ) {
        span.setAttribute("foo", "bar");
      },
    },
  },
})

Tip

It may help to put telemetry code in its own location and import it directly at the top of your main or index file.

import "./telemetry";

// other code