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

@loggy/adapter-nodejs

v0.1.7

Published

Adapter to monitor NodeJS web servers.

Downloads

28

Readme

LOGGY adapter for NodeJS

Adapter to monitor NodeJS web servers.

Usage

Install the adapter with npm i --save @loggy/adapter-nodejs or yarn add @loggy/adapter-nodejs.

Configuration

Require the adapter at the top of your server and pass the configuration to the init function.

const loggy = require('@loggy/adapter-nodejs');

loggy.init({ ticket: '2ATNP1AD70' });

The following options are available.

Ticket

The ticket is the only mandatory information. Each service has an unique ticket and all events sent with this ticket will be attached to the corresponding service.

Badges

Badges contain individual information that will be attached to the event. A badge must be of type string.

loggy.init({
    ticket: '2ATNP1AD70',
    badges: {
        cluster: 'EU',
        serverId: process.env.SERVER_ID
    }
});

Instance

Determines to which LOGGY instance the adapter should connect. By default it connects to the production instance. Set the property to demo to connect to the LOGGY demo instance. If you set it to local it will connect to your local LOGGY instance at http://localhost:2800.

loggy.init({
  instance: 'demo',
  ticket: '2ATNP1AD70'
});

Endpoint

Set the endpoint property to connect to your individual LOGGY instance at a given address. Please notice that the endpoint property will be preferred to the instance property.

loggy.init({
  endpoint: 'https://loggy.example.com',
  ticket: '2ATNP1AD70'
});

Testing

To test if everything works you can just try to execute an undefined function like so.

loggy.init({
  instance: 'demo',
  ticket: '2ATNP1AD70'
});

test();

Middleware

If you are using Express, you can also add the LOGGY middleware at the end of your routes.

app.use(loggy.errorHandler);

The middleware will send all errors to LOGGY before passing them to the next middleware.

Emit errors manually

You can also emit errors manually by passing an error instance to the emitError method. This is handy for building your own error handling logic.

try {
    const result = 10 * number;
} catch (error) {
    loggy.emitError(error);
}

You can also add dynamic badges to a specific error if you want to provide additional information. This can be useful if you, for example, want to identify the user, who is affected by the error.

try {
    const result = 10 * number;
} catch (error) {
    loggy.emitError(error, { user: req.user.id });
}