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

@thebosco/the-bosco-server-logger

v1.0.5

Published

Server-side logging package

Downloads

3

Readme

Server Logger

This package provides server-side logging for Node applications. Logging will be sent to Papertrail with the specified hostname when configured to do so. All properties of the package are configurable, but new Transports require development on this package, as the assumption is that only StdOut and Papertrail are supported. The following methods and parameters can be utilized to log:

Levels

This package allows for logging to happen according to the following levels, which correspond to a distinct degree of priority or urgency:

Critical: Application functionality is impaired.
Error: An error is occuring within the application, but no functionality is missing.
Warn: A message that could indicate a problem, but does not alter functionality or change the user's experience.
Info: Information that is required to understand the functionality of the method.
Debug: Additional information to help understand why certain behavior may be ocurring.

Message

A message to be sent to the logging transport. String interpolation is fine, and welcomed. Ideal messages are ones that can be searched with an easy prefix that results in all of the logs being displayed sequentially. For instance:

# GOOD:
log.info('dayAfterCron:NY: Found 13 New Events to Send Day After Emails To.')
...
log.critical(`dayAfterCron:NY: Event #${event.id} Missing Producer Email. Cannot Send!`)

# BAD:
log.info('Found 13 New Events to Send Day After Emails To.')
log.critical(`Event #${event.id} Missing Producer Email. Cannot Send!`)

In the first example, users on Papertrail can search for dayAfterCron:NY: to find all the relevant logs. In the latter, they cannot perform any individual search that would allow the logs to be visible in order.

Additional Data & Errors

Additional data and errors can be passed along to the package with the second parameter, but must be structured as follows:

log.info(message, {data: Object, error: Error or InternalError})

If not provided as objects in this way, these values will not be logged.

Implementation

# papertrailHostname is optional, and should not be provided in development environments.
# All hostnames are provided on an assignment-basis only. If you do not have one, please
# speak with a member of The Bosco's Engineering Team.

global.log = require('@thebosco/the-bosco-server-logger')({papertrailHostname: 'name-of-host')

global.log[level](message, {data, error})

Contributions

For information on contributing to this package, please see The Bosco Internal Error where up to date information on contribution requirements are to be found.