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

heroku-jmx

v1.0.4

Published

Heroku JMX tool

Downloads

3

Readme

Heroku CLI Plugin for JMX

Uses ngrok to tunnel a JMX connection into a dyno.

$ heroku plugins:install heroku-jmx

JMX Demo

Usage

Initialize your app (you'll need your ngrok auth token):

$ heroku jmx:init

Deploy your app:

$ git push heroku master

Look through your logs for this:

$ heroku logs -t
...
2016-06...app[web.1]: Start JConsole: heroku jmx:jconsole [email protected] 0.tcp.ngrok.io:13379

Then run that command:

$ heroku jmx:jconsole [email protected] 0.tcp.ngrok.io:13379

JConsole will open and information that it is an insecure connection (but it's actually secured via SSH).

To use VisualVM, leave the jmx:jconsole command running. Then set the VisualVM SOCKS proxy manually to localhost:1080.