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

chronos

v0.1.0

Published

Log cronjob results to graylog2

Downloads

206

Readme

chronos

Install

After you got nodejs (which includes npm now), you can just:

`npm install -g chronos`

And that's it.

Configuration

chronos should be compatible with every service that supports AMQP. You can configure chronos by placing a JSON file in /etc/chronos.json or /usr/local/etc/chronos.json. Example:

{
	"amqp" : {
		"host" : "10.0.13.1",
		"port" : 5672,
		"login" : "guest",
		"password" : "guest",
		"vhost" : "/",
		"key" : "somekey"
	},
	"stage" : "production"
}

If you don't set one of those, the defaults apply:

{
	"amqp" : {
		"host" : "127.0.0.1",
		"port" : 5672,
		"login" : "guest",
		"password" : "guest",
		"vhost" : "/",
		"key" : "logging"
	},
	"stage" : false
}

Usage

Let's say your current crontab looks something like this:

0 * * * * date >> /var/log/cronjobs/myjob.log && php /var/www/myapp/cli/index.php --some=bar

If you just replace this by:

0 * * * * chronos -s mystage -j myjob 'php /var/www/myapp/cli/index.php --some=bar'

From now on chronos will log the results of your cronjobs to graylog2.

Options

The cli options of chronos are:

  • jobname: (-j, required) Name of the cronjob, any string will do.
  • stage: (-s) Define a stage, if none is given the one in /etc/chronos.json is added
  • stdout: (-o) Add stdout output to log
  • stderr: (-e) Add stderr output to log
  • env: (-v) Add all environment variables to the log

Examples

chronos -oj job1 'printf "This output will be added to the log"'

chronos -j job2 'printf "This will trigger an Error-level message"; exit 1;'