Ship AWS Cloudwatch metrics to various backends. Once per minute, cloudwatch-conveyor will pull metrics from Cloudwatch and ship them to the backend of your choice.

Author

Norman Joyner - norman.joyner@gmail.com

Getting Started

Installing via NPM

npm install -g cloudwatch-conveyor

Running locally

cloudwatch-conveyor

Configuration

Environment Variables

AWS_ACCESS_KEY_ID - AWS access key id (required)
AWS_SECRET_ACCESS_KEY - AWS secret access key (required)
AWS_REGION - AWS region to pull metrics from (defaults to us-east-1)
BACKEND_NAME - backend to ship metrics to (defaults to stdout)
GRAPHITE_HOST - graphite server host (defaults to localhost)
GRAPHITE_PORT - graphite server port (defaults to 2003)
INFLUXDB_HOST - influxdb server host (defaults to localhost)
INFLUXDB_PORT - influxdb server port (defaults to 8086)
INFLUXDB_USERNAME - influxdb username (required for use with influxdb backend)
INFLUXDB_PASSWORD - influxdb password (required for use with influxdb backend)
INFLUXDB_DATABASE - influxdb database (defaults to cloudwatch-metrics)

Available Metrics

ELB
- Latency [Average | Maximum]
- RequestCount [Sum]
- HTTPCode_ELB_5XX [Sum]

Available Backends

Graphite
InfluxDB
Stdout

Contributing

Please feel free to contribute by opening issues and creating pull requests!

Keywords

FAQs

What is cloudwatch-conveyor?

Is cloudwatch-conveyor well maintained?

Package last updated on 14 Feb 2016

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

cloudwatch-conveyor