Skip to content

Commit

Permalink
done updating docs for #15
Browse files Browse the repository at this point in the history
  • Loading branch information
dirkraft committed Jan 18, 2016
1 parent b9db386 commit de0273a
Showing 1 changed file with 2 additions and 4 deletions.
6 changes: 2 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -146,7 +146,7 @@ Duplicate submission support __token*__: Neither the CloudWatch service nor web
([see CloudWatch documentation](http://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/cloudwatch_concepts.html#Dimension)).
For convenience, we can just submit these metrics in duplicate, once with the dimension and once without (the aggregate over all values of this dimension).

What follows is a detailed example of how you might name your metrics to submit them to CloudWatch in number of specific ways.
The following example shows how you might name your metrics to submit them to CloudWatch to accomplish this.


##### Example metric naming #####
Expand All @@ -155,8 +155,6 @@ We have multiple machines in the *Service X* cluster. We want a count over all m
for individual machines. To submit to each machine-specific and machine-ignornat, we
name the counter **ServiceX Requests machine={insert machine id here}**.

> Measuring: Number of Requests to Service X, is a code hale Counter with metric name "ServiceX Requests"
In this example, this turns out to be

```java
Expand Down Expand Up @@ -192,7 +190,7 @@ Any *name token* can be permuted by appending it with `*`, not just dimensions.
can grow exponentially such as in this example.

```java
registry.counter("ServiceX Requests group-tag* machine=1.2.3.4* strategy=dolphin* environment=development");
metricRegistry.counter("ServiceX Requests group-tag* machine=1.2.3.4* strategy=dolphin* environment=development");
```

This resolves to all of the following CloudWatch metrics.
Expand Down

0 comments on commit de0273a

Please sign in to comment.