2013-04-16 22:50:21 +02:00
|
|
|
# The form of each line in this file should be as follows:
|
|
|
|
#
|
|
|
|
# output_template (frequency) = method input_pattern
|
|
|
|
#
|
|
|
|
# This will capture any received metrics that match 'input_pattern'
|
|
|
|
# for calculating an aggregate metric. The calculation will occur
|
|
|
|
# every 'frequency' seconds and the 'method' can specify 'sum' or
|
|
|
|
# 'avg'. The name of the aggregate metric will be derived from
|
|
|
|
# 'output_template' filling in any captured fields from 'input_pattern'.
|
|
|
|
#
|
|
|
|
# For example, if you're metric naming scheme is:
|
|
|
|
#
|
|
|
|
# <env>.applications.<app>.<server>.<metric>
|
|
|
|
#
|
|
|
|
# You could configure some aggregations like so:
|
|
|
|
#
|
|
|
|
# <env>.applications.<app>.all.requests (60) = sum <env>.applications.<app>.*.requests
|
|
|
|
# <env>.applications.<app>.all.latency (60) = avg <env>.applications.<app>.*.latency
|
|
|
|
#
|
|
|
|
# As an example, if the following metrics are received:
|
|
|
|
#
|
|
|
|
# prod.applications.apache.www01.requests
|
|
|
|
# prod.applications.apache.www01.requests
|
|
|
|
#
|
|
|
|
# They would all go into the same aggregation buffer and after 60 seconds the
|
|
|
|
# aggregate metric 'prod.applications.apache.all.requests' would be calculated
|
|
|
|
# by summing their values.
|
|
|
|
#
|
|
|
|
# Note that any time this file is modified, it will be re-read automatically.
|
|
|
|
|
2013-05-20 22:29:59 +02:00
|
|
|
# NOTE: If you use the `sum` aggregation method, make sure the aggregation period is
|
|
|
|
# 5 seconds unless you know what you are doing. statsd pushes to carbon
|
|
|
|
# every 5 seconds (see local.js), so aggregating over a longer period of time
|
|
|
|
# will inflate the output value
|
|
|
|
|
2016-03-31 03:39:51 +02:00
|
|
|
# Aggregate all per-bucket remote cache stats into a generic hit/miss stat
|
2013-05-20 22:29:59 +02:00
|
|
|
stats.<app>.cache.all.hit (5) = sum stats.<app>.cache.*.hit
|
|
|
|
stats.<app>.cache.all.miss (5) = sum stats.<app>.cache.*.miss
|
2013-05-01 17:33:38 +02:00
|
|
|
|
2016-03-31 03:39:51 +02:00
|
|
|
# Aggregate all per-bucket remote cache stats counts into a generic hit/miss stat
|
2013-09-17 20:18:15 +02:00
|
|
|
stats_counts.<app>.cache.all.hit (5) = sum stats_counts.<app>.cache.*.hit
|
|
|
|
stats_counts.<app>.cache.all.miss (5) = sum stats_counts.<app>.cache.*.miss
|
|
|
|
|
2013-05-01 17:33:38 +02:00
|
|
|
# Aggregate all per-domain active stats to overall active stats
|
2013-05-20 22:29:59 +02:00
|
|
|
stats.gauges.<app>.users.active.all.<bucket> (5) = sum stats.gauges.<app>.users.active.*.<bucket>
|
2013-09-05 21:39:57 +02:00
|
|
|
stats.gauges.<app>.users.reading.all.<bucket> (5) = sum stats.gauges.<app>.users.reading.*.<bucket>
|
2013-11-06 17:23:19 +01:00
|
|
|
|
|
|
|
# Aggregate all per-realm end-to-end send stats to overall
|
2013-12-06 00:22:21 +01:00
|
|
|
stats.timers.<app>.endtoend.send_time.all.<type> (5) = sum stats.timers.<app>.endtoend.send_time.*.<type>
|
|
|
|
stats.timers.<app>.endtoend.receive_time.all.<type> (5) = sum stats.timers.<app>.endtoend.receive_time.*.<type>
|
|
|
|
stats.timers.<app>.endtoend.displayed_time.all.<type> (5) = sum stats.timers.<app>.endtoend.displayed_time.*.<type>
|
2013-12-06 00:22:25 +01:00
|
|
|
|
|
|
|
# Aggregate all per-realm narrow timing stats
|
|
|
|
stats.timers.<app>.narrow.initial_core.all.<type> (5) = sum stats.timers.<app>.narrow.initial_core.*.<type>
|
|
|
|
stats.timers.<app>.narrow.initial_free.all.<type> (5) = sum stats.timers.<app>.narrow.initial_free.*.<type>
|
|
|
|
stats.timers.<app>.narrow.network.all.<type> (5) = sum stats.timers.<app>.narrow.network.*.<type>
|
2014-02-13 18:49:44 +01:00
|
|
|
|
|
|
|
# Do the same for unnarrow times
|
|
|
|
stats.timers.<app>.unnarrow.initial_core.all.<type> (5) = sum stats.timers.<app>.unnarrow.initial_core.*.<type>
|
|
|
|
stats.timers.<app>.unnarrow.initial_free.all.<type> (5) = sum stats.timers.<app>.unnarrow.initial_free.*.<type>
|