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

@firstclasspostcodes/metrics

v1.2.0

Published

Provides easy integration for instrumenting code using custom CloudWatch metrics.

Downloads

34

Readme

Metrics

We use this library internally to easily integrate AWS CloudWatch Custom Metrics into our applications.

To get started:

npm i @firstclasspostcodes/metrics -s

Now, add a configuration file named metrics.config.js to the working directory. This library uses cosmiconfig so name your file accordingly.

module.exports = {
  // Required: this is the namespace that all custom metrics will be published with
  namespace: 'Test/Service',
  // Required: the AWS region that the metrics will be published to
  region: process.env.AWS_REGION,
  // Optional: for serverless functions, specify `manualMode` to ensure that a metric
  // flush interval is not started.
  manualMode: true,
  // Required: define the custom metrics available to the application at runtime.
  metrics: {
    // this is the key that a custom metric will be configured as
    interestingMetric: {
      // Optional: a list of dimensions for the metric
      dimensions: [
        {
          Name: 'Function',
          Value: 'normalHandler',
        },
      ],
      // Optional: define the resolution for the metric, 1-60. Defaults to 60.
      resolution: 1,
      // Required: the type of metric being recorded
      unit: 'Count/Second',
    },
    longRunningFunction: {
      dimensions: [
        {
          Name: 'Function',
          Value: 'testHandler',
        },
      ],
      resolution: 1,
      // For measured functions, use milliseconds
      unit: 'Milliseconds',
    },
  },
};

For any deployed AWS applications, the correct IAM permissions must be configured:

Function:
  Type: 'AWS::Serverless::Function'
  Properties:
    # ...
    Policies:
      - CloudWatchPutMetricPolicy: {}

or defined explicitly:

Statement:
  - Effect: Allow
    Action:
      - cloudwatch:PutMetricData
    Resource:
      - '*'

Given the configuration above, you can use the configured metrics in the following way:

const metrics = require('@firstclasspostcodes/metrics');

const { longRunningFunc } = require('./example');

exports.handler = async (event) => {
  metrics.interestingMetric(event.someValue.length);

  // record the same metric with a custom dimension
  metrics.interestingMetric(event.someValue.length, [{
    countryName: 'United States',
  }])

  const data = await metrics.longRunningFunction(() => {
    // this will measure how long it takes to execute using perf_tools
    return longRunningFunc(event.someValue);
  }));

  // will log a warning to the console and ignore this
  metrics.doesNotExistMetric();

  // for lambda functions, make sure to flush metrics
  // before execution ends
  await metrics.flush();

  return data;
};