Armonite

Introduction

A distributed Load testing tool designed for maximum destruction of target servers. It is capable of overloading servers by allowing you configure agents known as nukelets to carry out the assault.

The plan is just a simple json data specifying metadata such as,

• Request interval,
• Request payload data
• Interval delay.

Armonite Master

Master is the central component of the armonite warhead. It send commands to nukelets to carry out the destruction. it is capable of sending request in any fashion as specified in the master.config.yaml configuration. You specify load parameters to the which is saved locally for reuse and converted to a test plan for agents. The master also requires connections to local storage to persist load profiles and test results for future reviews.

Armonite causes destruction by runiing nukelets which in turn run threads that

Supported Configuration

• WH_MASTER_PORT
• WH_MONGO_CONNECTION
• WH_INFLUX_CONNECTION
• WH_LOG_PREFIX
• WH_GITHUB_REPO
• WH_GITHUB_USERNAME
• WH_GITHUB_TOKEN
• WH_STATSD_UDP_PORT

Nukelets

Nueklets are responsible for sending out request to target servers. The master can get them to call arbitrary targets or they can execute custom scripts that handles the request.

Warhead Agent Variables

• WH_MASTER_HOST
• WH_AGENT_PORT
• WH_ENABLE_DEBUG
• WH_METRIC_SAMPLING

Load Strategy

The Armonite console lets you confiugure how your agent will send requests either concurrently or sequentially

UI Console

The master is responsible for rendering the UI console