Fix graphite metrics

Bug #1049220 reported by Anthony Lenton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ratings and Reviews server
Confirmed
Low
Unassigned

Bug Description

Looking at the Graphite metrics currently stored, every "count" metric is constant 1.0.
It might make sense to change these for rate metrics, like ca.staging.rnr.*.request_time is.

Changed in rnr-server:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Łukasz Czyżykowski (lukasz-czyzykowski) wrote :

From what I suspect this could be a graphite misconfiguration, not really a problem with metrics. According to this http://stackoverflow.com/a/12170445 we probably don't generate enough data for it to cross aggregation threshold.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.