Change in osmo-bsc[master]: add time_cc API: cumlative counter for time, reported as rate_ctr

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.

pespin gerrit-no-reply at lists.osmocom.org
Tue Nov 2 11:05:38 UTC 2021


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:

> Patch Set 1:
> For all_allocated, it is the number of seconds that all channels were allocated per a given amount of time. For example, if the VTY shows all_allocated:sdcch of 10/min, it means all channels were allocated for 10 seconds of the last minute. For a stat item, getting this "per time" part is a complex problem.

Thanks, this is the kind of example I was asking for on my first comments in order to understand better what you want to achieve.

> > So I'm not really following on why you need all this infrastructure sorry,
> 
> I would appreciate if your criticism could be qualified as well as constructive.
> What do you mean by "all this"? What do you suggest instead?

Maybe the problem is that I don't see this may be the correct way to go here. I have the feeling we are adding too much counting complexity inside our code base, where this can be simply be submitted over time as a osmo_stat item counter, and let whatever system the customer uses to plot the data over time (eg using grafana or some custom statsd/python scripts) and see when the all_allocated:sdcch incremented over time. So that's what I'm suggesting.
Let's let other specialized systems do this kind of stuff instead of bloating our code base. I'm not blocking this if still others think it is a good idea to have this merged.


-- 
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 <nhofmeyr at sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: laforge <laforge at osmocom.org>
Gerrit-CC: pespin <pespin at sysmocom.de>
Gerrit-Comment-Date: Tue, 02 Nov 2021 11:05:38 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20211102/2a315dee/attachment.htm>


More information about the gerrit-log mailing list