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

@mailbots/logger

v0.4.1

Published

Internal MailBots tool for aggregating LogDNA and Datadog into a nice, unified logger

Downloads

30

Readme

MailBots Logger

A custom logger for the monitoring tools we use internally at FollowUpThen and MailBots: – Datadog and LogDNA.

LogDNA gets logs for debugging. The logger turns log events into datadog metrics, allowing us to view frequency of log events in dashboards, alerts and enable anomoly detection, etc.

Usage

const Logger = require("@mailbots/logger");
const logger = new Logger({
  logDnaKey: process.env.LOGDNA_KEY,
  logDnaHost: process.env.LOGDNA_HOSTNAME,
  logDnaApp: process.env.LOGDNA_APPNAME,
  ddAppKey: process.env.DATADOG_APP_KEY,
  ddApiKey: process.env.DATADOG_API_KEY,
  ddMetricsPrefix: process.env.DATADOG_METRICS_PREFIX || "", // to keep microservice metrics organized
  logToConsole: process.env.LOG_TO_CONSOLE // log to console.log. Pass "short" not pass extra data
});

// A simple log message
logger.log("a simple log message");

Set Logging Context

Set context from webhook. Every subsequent log event in that the request shares this context, allowing for searching by userid or session-id.

logger.setContextFromWebhook(webhook);

You can also set logging context from the AWS Lambda context object.

logger.setLambdaContext(context);

Caution: Data Types

When passing debug data in the data param, data types need to remain consistent (LogDNA requirement for their indexing feature). As a convention, always imply the datatype of the debug var in the key name.

logger.log("a log message", { level: "info", data: { debug_str: "data" } });

Debugging

Run tests with DEBUG=@mailbots/logger to tests our parts and datadog. Runt tests with NODE_DEBUG=logdna to see logdna output.

Here's an .env template to copy / paste:

LOGDNA_KEY=
LOGDNA_HOSTNAME=
LOGDNA_APPNAME=
NODE_ENV=

DATADOG_API_KEY=
DATADOG_APP_KEY=
DATADOG_METRICS_PREFIX=

Available logging services

Besides logging the message to the console, the library also sends it to our third-party logging services:

  • LogDna
  • DataDog

A log message can opt out of individual services by passing a boolean param to the options object:

logger.log("a log message", { datadog: false, logdna: false });