|
|
@@ -10,7 +10,7 @@ Eloy Coto Pereiro
|
|
|
|
|
|
<[email protected]>
|
|
|
|
|
|
- Copyright © 2014 Eloy Coto
|
|
|
+ Copyright © 2014 Eloy Coto
|
|
|
__________________________________________________________________
|
|
|
|
|
|
Table of Contents
|
|
|
@@ -125,10 +125,10 @@ failure_route[tryagain] {
|
|
|
3.2. statsd_gauge(key, value)
|
|
|
|
|
|
Gauges are a constant data type. They are not subject to averaging, and
|
|
|
- they donât change unless you change them. That is, once you set a gauge
|
|
|
+ they don't change unless you change them. That is, once you set a gauge
|
|
|
value, it will be a flat line on the graph until you change it again.
|
|
|
|
|
|
- Gauges are useful for things that are already averaged, or donât need
|
|
|
+ Gauges are useful for things that are already averaged, or don't need
|
|
|
to reset periodically
|
|
|
|
|
|
This function can be used in ALL ROUTES.
|
|
|
@@ -153,7 +153,7 @@ route [gauge_method]{
|
|
|
the statsd server collects all timers under the stats.timers prefix,
|
|
|
and will calculate the lower bound, mean, 90th percentile, upper bound,
|
|
|
and count of each timer for each period (by the time you see it in
|
|
|
- graphite, thatâs usually per minute).
|
|
|
+ graphite, that's usually per minute).
|
|
|
|
|
|
Example 1.5. statsd_start usage
|
|
|
...
|
Daniel-Constantin Mierla