First pass at pulling metrics from AWS ELBs #56
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Sweeeet! :) |
aphyr
added a commit
that referenced
this pull request
Aug 7, 2013
First pass at pulling metrics from AWS ELBs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've put together a first pass at pulling ELB metrics from AWS CloudWatch.
#9 talks about adding cloudwatch support, which I thought about doing, but I thought it might turn into a sprawling tool - and maybe it's preferred to target the individual services?
This will connect to cloudwatch and pull the metrics for all of the ELB as listed in the CloudWatch Developer Guide.
You can report metrics for different load balancers, the event host is setup to be the load balancer name (which makes sense in my org, but it's something I can add code into so it can be overridden if you think that's a bit too prescriptive).
It supports using a fog credentials file, or passing in your api keys on the command line.
By default it will only show the aggregated metrics from all of the AZs in a region, however you can pass in a list of AZs to get the different metrics reported.