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

damage-report

v0.1.1

Published

Checks Artillery.io results for errors and thresholds for use in CI/CD pipelines

Downloads

1

Readme

Damage Report

Damage report can be run in your CI/CD pipeline to check the results of Artillery.io reports.

Installation

Easy, peasy

$ npm install -g damage-report

Running

Run an Artillery load test and output the results to a file

$ artillery run my-load-test.yaml -o performance.results.json

Afterward this is completed run a damage report

$ damage-report --file ./performance.results.json --median 50 --p95 95 --p99 100 --rps 50

If rules are broken then the process will return an exit code of 1

Options

$ damage-report --help
  • --median: Median threshold in ms
  • --p95: p95 threshold in ms
  • --p99: p99 threshold in ms
  • --rps: Mean requests per seconds required
  • --file: Location of the artillery results json (default: "./performance.results.json")

Example

 _____                                                               _
|  __ \                                                             | |
| |  | | __ _ _ __ ___   __ _  __ _  ___   _ __ ___ _ __   ___  _ __| |_
| |  | |/ _` | '_ ` _ \ / _` |/ _` |/ _ \ | '__/ _ \ '_ \ / _ \| '__| __|
| |__| | (_| | | | | | | (_| | (_| |  __/ | | |  __/ |_) | (_) | |  | |_
|_____/ \__,_|_| |_| |_|\__,_|\__, |\___| |_|  \___| .__/ \___/|_|   \__|
                               __/ |               | |
                              |___/                |_|
Version: x.x.x

Checking artillery results in ./performance.results.json for:

- Any errors
- Any 50x result codes
- Median response time < 50ms
- p95 response time < 95ms
- p99 response time < 100ms
- Requests per second > 50

Results:

✓ No errors found in results
✓ No 50x error codes found in results

|▓                             |         |    ✓   Median latency below threshold of 50ms at: 1.7ms
|▓▓▓                           |         |    ✓   p95 latency below threshold of 95ms at: 9.8ms
|▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓             |         |    ✓   p99 latency below threshold of 100ms at: 59.7ms

|▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓|▓▓▓▓▓    |    ✓   rps above threshold of 50 at: 59.76