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-queue-agent

v1.0.0

Published

PM2 Queue Agent Module

Downloads

5

Readme

Monitor, measure, and interact with managed processes via agent.

Features

  • Enhanced HTTP Interface
  • Pub/Sub metrics collector
  • Integration with PMX Dashboard

Available Endpoints

| Path | Description | |------|-------------| | / | list processes | | /list | list processes | | /status/{name} | status of process by name | | /metrics/{name} | metrics of process by name | | /stop/{name} | stop process by name | | /restart/{name} | restart process by name | | /scaleup/{name} | scale up process by name | | /scaledn/{name} | scale down process by name |

Default Port: 9808 The port can also be set via environment variable PM2_AGENT_HTTP_PORT

Available Actions

Each expects the name of a process as the parameter

  • stop
  • restart
  • scale up
  • scale down

Available Metrics

| Metric Type | Dashboard Name | Pub/Sub Type | |-------------|----------------|--------------| | METER | {process name} jobCompleted/sec | jobCompleted | | METER | {process name} jobFailed/sec | jobFailed | | METRIC | queueStatus {queue name} | status | | COUNTER | activeJobs {queue name} | activeJobs | | COUNTER | failedJobs {queue name} | failedJobs |

Metrics are collected from via Subscription to metrics:pub where the expected message payload has the following attributes:

{
    "type": "<metric name>",
    "from": "<process name>",
    "queue": "<queue name>",
    "data": {
        "value": "<actual value>"
    }
}

cote is used to provide the Publish/Subscribe transport mechanism for metrics.

Example Publisher

var Publisher = require('cote').Publisher;

var publisher = new Publisher({
    name: 'metricPublisher',
    broadcasts: ['metrics:pub']
});

publisher.on('ready', function () {
    var msg = {
        type: 'status',
        from: 'testApp1',
        queue: 'test',
        data: {
            value: 'online'
        }
    };
    publisher.publish('metrics:pub', msg);
});

Debugging

export NODE_DEBUG=agent

By setting the environment variable NODE_DEBUG to agent then additinal logging via util.debuglog will be displayed.