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

@sorrir/sorrir-logging

v2.1.0

Published

Logging repository for SORRIR projects.

Downloads

7

Readme

sorrir-logging

Logging tailormade for sorrir

Specifying the logging target

A HowTo log to ES can be found here.

If NODE_ENV is equal to 'production', we log to stdout. Otherwise, we check whether the environment variables SORRIR_ES_URL, SORRIR_ES_USER and SORRIR_ES_PASSWORD are set. If one is not, we log to stdout. Otherwise we log to the Elasticsearch instance specified via these environment variables.

The target index that is logged to can be configured via environment variables as well. The variable SORRIR_ES_INDEX can be used to log to a specific index. The variable SORRIR_ES_INDEX_PREFIX can be used to log to a date-dependent index (e.g. setting SORRIR_ES_INDEX_PREFIX to "hello" will make the logger log to the index hello-$timestamp_day). If both are specified, SORRIR_ES_INDEX_PREFIX is disregarded. If none are specified, the logger behaves as if SORRIR_ES_INDEX_PREFIX was set to "filebeat-debug".

For easy organisation, there is a possibility to add an additional key-value pair to logs when outputting to Elasticsearch. Setting the environment variable SORRIR_ES_DEBUG to your_value will cause the logs to possess the key-value pair fields.metadata.context.debug = your_value.