You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -28,9 +28,11 @@ The design goals of this library are the following:
28
28
29
29
## Limitations & compromises
30
30
31
-
Due to limited number of locks employed, there is no strong consistency guarantee between different metrics. If a particular thread changes two counters and serialization happens in the middle, you may see a value for one counter increasing but not for the other - until the next time metrics are collected. Hence, care must be taken when creating alerts based on metrics differential. Another compromise stemming from minimized locking requirements is inability to _remove_ metrics from a `Registry` - however, that is something which is not supported by Prometheus anyway
32
-
33
-
Boost::accumulators do not correctly work under MacOS, which prevents Summary class from working - more throrough investigation pending
31
+
* Due to limited number of locks employed, there is no strong consistency guarantee between different metrics
32
+
* If a particular thread changes two counters and serialization happens in the middle, you may see a value for one counter increasing but not for the other - until the next time metrics are collected. Hence, care must be taken when creating alerts based on metrics differential
33
+
* For same reason, histogram 'sum' may be out of sync with total count - skewing the average value with ⅟n asymptotic upper bound
34
+
* It's not possible to _remove_ metrics from a `Registry` - conceptually shared with Prometheus
35
+
* Boost::accumulators do not correctly work under MacOS, which prevents Summary class from working there - more throrough investigation pending
0 commit comments