pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/25973 )
Change subject: add time_cc API: cumlative counter for time, reported as rate_ctr ...................................................................... Patch Set 1: Well maybe then the question is why are you using rate_ctr and not stat_items here, it really confuses me. The point of rate_ctr is seeing how frequently some event happens over time, for instance shown in VTY: "device:rx_underruns: 0 (0/s 0/m 0/h 0/d) Number of Rx underruns" But my understanding here is that allAvailableSDCCHAllocated fits with a stat_item, which is simply a counter value changing over time. So I'm not really following on why you need all this infrastructure sorry, this all looks super complicated for no reason (I'm able to see). Maybe someone else can also shed some light on it. -- To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/25973 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-bsc Gerrit-Branch: master Gerrit-Change-Id: Icdd36f27cb54b2e1b940c9e6404ba9dd3692a310 Gerrit-Change-Number: 25973 Gerrit-PatchSet: 1 Gerrit-Owner: neels <nhofm...@sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-CC: pespin <pes...@sysmocom.de> Gerrit-Comment-Date: Thu, 28 Oct 2021 11:38:16 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: No Gerrit-MessageType: comment
