Skip to main content

Helper for pushing AWS CloudWatch metrics to Graphite

Project description

https://travis-ci.org/crccheck/cloudwatch-to-graphite.svg

Cloudwatch-to-Graphite (leadbutt) is a small utility to take metrics from CloudWatch to Graphite.

Installation

Install using pip:

pip install cloudwatch-to-graphite

Usage

Configuring boto

Cloudwatch-to-Graphite uses boto, so make sure to follow its configuration instructions. The easiest way to do this is to set up the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables.

Configuration Files

If you have a simple setup, the easiest way to get started is to set up a config.yaml. You can copy the included config.yaml.example. Then just run:

leadbutt

If you have several configs you want to switch between, you can specify a custom configuration file:

leadbutt --config-file=production.yaml -n 20

You can even generate configs on the fly and send them in via stdin by setting the config file to ‘-‘:

generate_config_from_inventory | leadbutt --config-file=-

Sending Data to Graphite

If your graphite server is at graphite.local, you can send metrics by chaining with netcat:

leadbutt | nc -q0 graphite.local 2003

Or if you want to use UDP:

leadbutt | nc -uw0 graphite.local 2003

If you need to namespace your metrics for a hosted Graphite provider, you could provide a custom formatter, but the easiest way is to just run the output through awk:

leadbutt | \
  awk -v namespace="$HOSTEDGRAPHITE_APIKEY" '{print namespace"."$0}' | \
  nc -uw0 my-graphite-provider.xxx 2003

Customizing Your Graphite Metric Names

Set the Formatter option to set the template used to generate Graphite metric names. I wasn’t sure what should be default, so I copied cloudwatch2graphite’s. Here’s what it looks like:

cloudwatch.%(Namespace)s.%(dimension)s.%(MetricName)s.%(statistic)s.%(Unit)s

TitleCased variables come directly from the YAML configuration, while lowercase variables are derived:

  • statistic – the current statistic since Statistics can be a list

  • dimension – the dimension value, e.g. “i-r0b0t” or “my-load-balancer”

The format string is Python’s %-style.

config.yaml

What metrics are pulled is in a YAML configuration file. See the example config.yaml.example for an idea of what you can do.

Developing

Install requirements:

pip install -r requirements.txt

Running test suite:

make test

Verifying tests run over all supported Python versions:

tox

Useful References

Prior Art

Cloudwatch-to-Graphite was inspired by edasque’s cloudwatch2graphite. I was looking to expand it, but I wanted to use boto.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

cloudwatch-to-graphite-0.3.0.tar.gz (5.8 kB view details)

Uploaded Source

Built Distribution

cloudwatch_to_graphite-0.3.0-py2.py3-none-any.whl (8.9 kB view details)

Uploaded Python 2 Python 3

File details

Details for the file cloudwatch-to-graphite-0.3.0.tar.gz.

File metadata

File hashes

Hashes for cloudwatch-to-graphite-0.3.0.tar.gz
Algorithm Hash digest
SHA256 9a9fc4179d0684ee0cd09f59696873d2b40bfb96e2080eef2f65a23e79b10d1b
MD5 16535f584738b809f9e18f17c8181e6b
BLAKE2b-256 00d83e985b74b8b592fbac84a1e50a392a5fff7220b0f3decd19e153721c0248

See more details on using hashes here.

Provenance

File details

Details for the file cloudwatch_to_graphite-0.3.0-py2.py3-none-any.whl.

File metadata

File hashes

Hashes for cloudwatch_to_graphite-0.3.0-py2.py3-none-any.whl
Algorithm Hash digest
SHA256 65339653ff980c57ca4a906c6fd364c6fd88b535691819fdfa2ec8188ac0e4fa
MD5 7aecdb4c36d91ec8717d006c813f88ae
BLAKE2b-256 03a8d55ea84b501029cd623e4d199aed9f1c25a61d8ae41056cbadef23fb3803

See more details on using hashes here.

Provenance

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page