Closed alexppg closed 4 years ago
I've been recollecting and playing with the metrics and I've seen that this way follows better metrics practices.
Coverage increased (+0.003%) to 99.195% when pulling 66423d66939d1ed57a4d41d2c9fd9b07e90e116e on feature/add_status_to_metrics_latency into 3495104dfac88833db4bf8adfd8730d6f3523c99 on master.
@hcamino I've made some more changes and fixed the tests, a re-review would be nice.
@avara1986 This "breaks" the prior metrics. Maybe it should be merged in a major release with it's changelog.
I've been recollecting and playing with the metrics and I've seen that this way follows better metrics practices.