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

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.

Usage

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.6.0.tar.gz (6.9 kB view details)

Uploaded Source

Built Distribution

cloudwatch_to_graphite-0.6.0-py2.py3-none-any.whl (10.2 kB view details)

Uploaded Python 2 Python 3

File details

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

File metadata

File hashes

Hashes for cloudwatch-to-graphite-0.6.0.tar.gz
Algorithm Hash digest
SHA256 eb4689463106c187cb31a346fc5224657d01b42763d2c70567e59887f16036e9
MD5 8b06b8c9e3798d53bed094ebcdb7bc39
BLAKE2b-256 310df69fd81e84e66cbd7afcd7ad984020252dc661b66e2f843d5469f268bb5f

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for cloudwatch_to_graphite-0.6.0-py2.py3-none-any.whl
Algorithm Hash digest
SHA256 befb92714da3a58af4ac6f8f46209c6ddb63809593afed2d3381b6c4cdf96824
MD5 0957489272c413a3ac5ec6dd9e08cc50
BLAKE2b-256 95fddeac76d584caec507d670ef9b86d4aac5a5ea2b8fd8ba33eb7f76d4ee6cd

See more details on using hashes here.

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