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

cloudwatch-producer

v0.0.1

Published

Simple scaffolding for applications that produce batched CloudWatch metrics

Downloads

3

Readme

cloudwatch-producer

Note This project is a work in progress at the moment and not fully ready for production!

NPM downloads Build Status

Simple scaffolding for applications that produce batched CloudWatch metrics

Installation

npm install cloudwatch-producer

Usage

import { Producer } from 'cloudwatch-producer';

// create simple producer
const producer = Producer.create({
  region: 'eu-west-1'
});

Credentials

By default the consumer will look for AWS credentials in the places specified by the AWS SDK. The simplest option is to export your credentials as environment variables:

export AWS_SECRET_ACCESS_KEY=...
export AWS_ACCESS_KEY_ID=...

If you need to specify your credentials manually, you can use a pre-configured instance of the CloudWatch Client.

import { Producer } from 'cloudwatch-producer';
import { CloudWatchClient } from '@aws-sdk/client-cloudwatch';

// create simple producer
const producer = Producer.create({
  region: 'eu-west-1',
  cloudwatch: new CloudWatchClient({
    region: 'eu-west-1',
    credentials: {
      accessKeyId: 'yourAccessKey',
      secretAccessKey: 'yourSecret'
    }
  })
});

Sending Metrics

To send a metric, you just need to call the .collect() method with your metric and value, as in the example below.

import { Producer } from 'cloudwatch-producer';

// create simple producer
const producer = Producer.create({
  region: 'eu-west-1'
});

producer.collect(
  {
    MetricName: 'My Awesome Metric',
    Unit: 'Seconds',
    Dimensions: [
      {
        Name: 'dimension-one',
        Value: 'dimension-one-value'
      }
    ]
  },
  2
);

Please note that if you have not started the producer, this metric will be sent instantly, rather than in a batch. You can find out how to start batching below.

Batching Metrics

By default, CloudWatch Producer will not send metrics in batches until the producer has been started, to start it, just call the .start() method like so:

producer.start();

Stop Batching Metrics

If you would like to stop sending metrics in batches and go back to instantly sending metrics, just call the .stop() method like so:

producer.stop();

What gets sent to CloudWatch?

CloudWatch Producer will send the following via the API when a metric batch is triggered or a metric is instantly dispatched:

{
  MetricName: "My Awesome Metric",
  Dimensions: [
    {
      Name: 'dimension-one',
      Value: 'dimension-one-value'
    }
  ],
  StatisticValues: {
    Maximum: 2,
    Minimum: 2,
    SampleCount: 1,
    Sum: 2
  },
  Timestamp: "Thu Mar 02 2023 22:26:20 GMT+0000 (Greenwich Mean Time)",
  Unit: "Seconds"
}
  • If no Dimensions were supplied when the metric was collected, it will be sent as []
  • If a Unit was not supplied when the metric was collected, it will be sent as None
  • Timestamp is automatically set as the date and time that the metric collection was triggered
  • If you are batching requests, the metric will be updated
    • The values within StatisticValues will be incremented like so:
      • Maximum will either be the previously stored value or the provided value if the provided value is higher
      • Minimum will either be the previously stored value or the provided value if the provided value is lower
      • SampleCount will be incremented each time the metric is updated
      • Sum will be the previously stored value plus the provided value

Development

Test

npm test

Coverage

For coverage report, run the command:

npm run coverage

Lint

To check for problems using ESLint

npm run lint

Contributing

See contributing guidelines