Skip to content

Commit

Permalink
Merge pull request statsd#199 from Dieterbe/null_counter
Browse files Browse the repository at this point in the history
document reset-to-0 behavior for counters
  • Loading branch information
mrtazz committed Dec 9, 2012
2 parents 1e47f71 + f3d58af commit b1d3905
Showing 1 changed file with 7 additions and 4 deletions.
11 changes: 7 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,16 +22,19 @@ etc)
general values should be integer.

* *flush*
After the flush interval timeout (default 10 seconds), stats are
aggregated and sent to an upstream backend service.
After the flush interval timeout (defined by `config.flushInterval`,
default 10 seconds), stats are aggregated and sent to an upstream backend service.

Counting
--------

gorets:1|c

This is a simple counter. Add 1 to the "gorets" bucket. It stays in memory
until the flush interval `config.flushInterval`.
This is a simple counter. Add 1 to the "gorets" bucket.
At each flush the current count is sent and reset to 0.
If the count at flush is 0 then you can opt to send no metric at all for
this counter, by setting `config.deleteCounters` (applies only to graphite
backend). Statsd will send both the rate as well as the count at each flush.

### Sampling

Expand Down

0 comments on commit b1d3905

Please sign in to comment.