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

pm2-loggly

v1.1.1

Published

PM2 Remote Logging to Loggly

Downloads

23

Readme

pm2-loggly

PM2 Remote Logging to Loggly

NPM

Installation

pm2 install pm2-loggly

Configuration

Default Configuration

You can see this inside of package.json.

"config": {
  "logglyClient": {
    "token": "your-token",
    "subdomain": "your-subdomain",
    "tags": "your-tag-1,your-tag-2"
  },
  "pm2Apps": "your-app-1,your-app-2"
}
Explanation of Configuration Options
  • logglyClient.token: a token from https://your-subdomain.loggly.com/tokens
  • logglyClient.subdomain: your Loggly subdomain
  • logglyClient.tags: a comma-delimited list of global tags applied to all logs
  • pm2Apps: a comma-delimited list of apps allowed to log to Loggly (logs will be tagged with the app name as well)
Recommended Way of Setting the Configuration Options

In your terminal run each of these commands:

pm2 set pm2-loggly.logglyClient.token my-extra-long-token-from-loggly
pm2 set pm2-loggly.logglyClient.subdomain mylogglysubdomain
pm2 set pm2-loggly.logglyClient.tags tag1,tag2,tag3
pm2 set pm2-loggly.pm2Apps app1,app2,app3
Optional Way of Setting the Configuration Options
  1. Edit ~/.pm2/module_conf.json and add something like this inside the first {}:
"pm2-loggly": {
  "logglyClient": {
    "token": "my-extra-long-token-from-loggly",
    "subdomain": "mylogglysubdomain",
    "tags": "tag1,tag2,tag3"
  },
  "pm2Apps": "app1,app2,app3"
}
  1. Edit pm2-loggly/package.json and replace the default configuration above with:
"config": {
  "logglyClient": {
    "token": "my-extra-long-token-from-loggly",
    "subdomain": "mylogglysubdomain",
    "tags": "tag1,tag2,tag3"
  },
  "pm2Apps": "app1,app2,app3"
}