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

stackify-logger

v3.1.0

Published

Stackify logs and errors for Node.Js

Downloads

1,186

Readme

npm version

Stackify Log API for Node.js

  • Errors and Logs Overview: - http://support.stackify.com/errors-and-logs-overview/
  • Sign Up for a Trial: http://www.stackify.com/sign-up/

Installation

$ npm install stackify-logger

Usage

var stackify = require('stackify-logger');

// this should be executed only once in the app
stackify.start({apiKey: '***', appName: 'Node Application', env: 'dev'});

The following options could be passed to the start method:

  • apiKey (Required): Stackify API key
  • appName (Required): Application name
  • env (Required): Environment name. If a Stackify agent is installed, this does not need to be set. If a Stackify agent is not installed, this should be set to the environment name.
  • proxy: HTTP proxy
  • debug: Enables internal debug logging for troubleshooting. Defaults to false.
  • logServerVariables: Enables adding server variables to error logs. Defaults to true.

Notice: When calling process.exit(), the stackify-logger will synchronously send log messages that have been queued but not transmitted. Sending via proxy wouldn't be possible in this case.

Using direct logger

If you are not using Winston logger you can use default Stackify logger. It has 6 levels of messages: trace, debug, info, warn, error, and fatal. To send the message to Stackify API you should run one of the following methods in any place of your code where you want to track some information:

stackify.log(level, message [, meta])
stackify.trace(message [, meta])
stackify.debug(message [, meta])
stackify.info(message [, meta])
stackify.warn(message [, meta])
stackify.error(message [, meta])
stackify.fatal(message [, meta])

Message must be a string.

meta - an additional parameter of any type.

Examples of usage:

// Add the module to all the script files where you want to log any messages.
var stackify = require('stackify-logger');

stackify.log('info', 'hey!');
stackify.debug('any message');
stackify.info('any message', {anything: 'this is metadata'});
stackify.warn('attention');
stackify.log('error', {error : new Error()});

When logging an error or fatal message you can pass an Error object in metadata like in the last example, so the exception details would be available.

Exception handling

By executing stackify.start() you set a handler for uncaught exceptions. Make sure you run it before any methods that set exception handlers.

Using with Express

Global handler doesn't work inside Express route methods. You should use error-handling middleware function stackify.expressExceptionHandler. Since middleware is executed serially, it's order of inclusion is important. Make sure you add it before any other error-handling middleware.

var express = require('express');
var app = express();

/* 
*** block of route handlers ***
*** *** **** **** **** **** ***
*/

app.use(stackify.expressExceptionHandler);

To handle exceptions correctly put this right after all route handlers.

Real User Monitoring (RUM)

Real user monitoring injects a script tag containing the RUM JS that is responsible for capturing information about the http requests on the browser. This approach is manual and needs to be configured.

RUM - Setup

let stackify = require('stackify-logger');

// Configuration
stackify.start({apiKey: '***', appName: 'Node Application', env: 'dev', rumKey: 'YourRumKey'});

// Use this on the view/controller handler
require('stackify-logger').injectRumContent()
// or
stackify.injectRumContent()

Troubleshooting

If logging isn't working, enable internal debug logging for Stackify by setting the debug flag in the Stackify options.

stackify.start({apiKey: '***', appName: 'Node Application', env: 'dev', debug: true});

You will see stackify-debug.log in your application's directory.

License

Copyright 2019 Stackify, LLC.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.