Merge lp:~caravone/txstatsd/statsd-timings-consistency into lp:txstatsd
Status: | Superseded |
---|---|
Proposed branch: | lp:~caravone/txstatsd/statsd-timings-consistency |
Merge into: | lp:txstatsd |
Diff against target: |
107 lines (+50/-6) 2 files modified
txstatsd/metrics/metrics.py (+15/-3) txstatsd/tests/test_metrics.py (+35/-3) |
To merge this branch: | bzr merge lp:~caravone/txstatsd/statsd-timings-consistency |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Sidnei da Silva | Approve | ||
Review via email: mp+83459@code.launchpad.net |
This proposal has been superseded by a proposal from 2011-11-28.
Commit message
Changed timing() method to clearly take durations in seconds and emit durations to txstatsd server in milliseconds
Add option for automatic calculation of timing duration
Description of the change
Updated Nov. 28, 2011:
Made sure ExtendedMetrics and IMetrics had the updated timing() logic as well. Added unit tests for ExtendedMetrics.
Changed timing() method to clearly take durations in seconds and emit durations to txstatsd server in milliseconds
Add option for automatic calculation of timing duration
Unmerged revisions
- 56. By Curtis Caravone
-
Formatting: Removed spaces around '=' in default function arguments
- 55. By Curtis Caravone
-
Added automatic timer support for ExtendedMetrics
Added unit tests for ExtendedMetrics - 54. By Curtis Caravone
-
Fixed timing call in ExtendedMetrics and IMetrics to match Metrics
- 53. By Curtis Caravone
-
[r=sidnei] Changed timing() method to clearly take durations in seconds and emit durations to txstatsd server in milliseconds
Add option for automatic calculation of timing duration - 52. By Sidnei da Silva
-
- Someone forgot to lint this.
- 51. By Lucio Torre
-
[r=sidnei,theiw] Add pluggable metric kind support to txstatsd.
- 50. By Ian Wilkinson
-
[r=sidnei] Resolve the host when instantiating the Twisted client.
- 49. By Sidnei da Silva
-
Delay importing the reactor such that other applications get a chance to pick their choice of reactor. [trivial]
- 48. By Lucio Torre
-
[r=sidnei] add probabilistic distinct counter
- 47. By Sidnei da Silva
-
Delay importing process module and reactor [trivial]
Looks good. Thanks!
One thing I noticed is that we're storing instance-level attributes here and in other metrics. Which means that we can't safely use them from different threads. We need to make sure that we use a per-thread metrics object in client code, or maybe handle the thread-safety here so the client code doesn't have to bother.