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

crashplan-logs

v1.0.3

Published

Script to parse and watch CrashPlan PRO backup logs in real time.

Downloads

18

Readme

CrashPlan for Small Business log viewer

Demo

This is a real time log viewer for CrashPlan for Small Business made with Node.js. It behaves pretty much like the tail command. It displays the logs with some color to be easily readable, and tries to compute the speed of upload with the data that's available in the logs. Keep in mind there are no guarantees at all - I made this for myself and thought I should open-source it.

Installation

npm i -g crashplan-logs

Usage

Usage: crashplan-logs {OPTIONS} [LOGFILE]

Standard options:

   --lines, -n  Number of lines to display initially.
                Defaults to 10.

  --follow, -f  If set, monitors the file for new lines and appends them to the output.
                If unspecified, exits after showing the initial number of lines.

By default, the script looks in the default CrashPlan log locations. You can manually specify the log file by providing as the last argument to the command.

Pre-requisites

This was coded with Node.js. It's not the most widely used scripting language, but that's what I'm the most comfortable with. Therefore, you will need Node.js version 4.9 or more to run this program. Head over to the official Node.js downloads section to install it if you don't already have it.

It was tested on Linux (Ubuntu 17.10) but it should also run fine on OSX and Windows (let me know if it doesn't).

My logs were produced by the Code42 6.7 application, but I don't think it differs a lot from version to version.

Motivation

With the forced migration of CrashPlan Home users to CrashPlan for Small Business, many people were pretty disappointed with the UI of the new client compared to what they were used to. There were many issues, but what I disliked the most personnally was the removal of any relevant info about the upload progress.

In CrashPlan Home it was possible to see the upload speed and the file currently uploading, which gave a pretty good idea of what was happening. Now all we have is an overall percentage of completion as well as the "done" and "remaining" totals (rounded to the nearest unit, which in the case of terabytes is pretty vague).

This little package aims to provide some details that the standard interface does not.

Limitations

One limitation is that the CrashPlan backup entries do not specify the seconds in their timestamp, only the minute. So for files uploading in less than 5 minutes, the speed might not be super accurate.

Also, CrashPlan logs other stuff not directly related to uploaded items in that log file. I try to ignore those lines, but it might happen that unexpected lines appear in the output. Don't worry, it's normal, I just didn't have the time (and knowledge) to cover all possible cases.