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-nginx-slack

v1.1.0

Published

PM2 Module to tail nginx error, access logs and send them to slack

Downloads

7

Readme

Nginx logs to Slack

Build Status

This module tails nginx error, access logs using node-tail and sends them to the specified slack channel.

Installation

pm2 install pm2-nginx-slack

Set slack webhook url

pm2 set pm2-nginx-slack:slack_access_log_url https://slack.url.com/ # Slack webhook to post access logs
pm2 set pm2-nginx-slack:slack_error_log_url https://slack.url.com/ # Slack webhook to post error logs

Defaults

{
    "slack_access_log_url": null,
    "slack_error_log_url": null,
    "access_log_path": "/var/log/nginx/access.log",
    "error_log_path": "/var/log/nginx/error.log",
    "tail_access_log": false,
    "tail_error_log": true,
    "status_codes": "400, 401, 403"
}
  • slack_access_log_url - Slack webhook URL to post access logs
  • slack_error_log_url - Slack webhook URL to post error logs
  • access_log_path - Path to your nginx access log(Default: /var/log/nginx/access.log)
  • error_log_path - Path to your nginx error log(Default: /var/log/nginx/error.log)
  • tail_access_log - Enable/Disable tailing access log(Default: false)
  • tail_error_log - Enable/Disable tailing error log(Default: true)
  • status_codes - HTTP status codes to filter access logs(Default: 400, 401, 403)

The above configurations can be modified with the following syntax and the changes are applied automatically by pm2.

pm2 set pm2-nginx-slack:tail_access_log true
pm2 set pm2-nginx-slack:access_log_path /path/to/your/nginx/access.log

Access logs

Access logs are disabled by default and can be enabled with the following command.

pm2 set pm2-nginx-slack:tail_access_log true

To filter nginx access logs, HTTP status codes 400, 401 & 403 are used by default. To enable filtering on custom HTTP status codes, use

pm2 set pm2-nginx-slack:status_codes "400, 404, 413" # Notice the comma-space seperated string

References

PM2-slack

License

License MIT