mirror of https://gerrit.osmocom.org/libosmocore
923cb84270
Exempt all stat_item statistics from 'stats reset'. Only reset rate_ctr statistics to zero. The rate_ctr statistics have an implicit time scale, counting occurences per time unit. For them it makes sense to reset all ratings and start from zero, for example in a test suite (e.g. our TTCN3 BSC_Tests). In contrast, stat_item statistics count number of objects or nr of specific object stati at any given time, and they do not deteriorate over time. Many stat items depend on increment/decrement to be sane. For example, in osmo-bsc, if the nr of connected BTS is 3, that does not make sense to be reset to zero. There are still 3 BTS connected, only the stat_item would suddenly reflect zero. From then on, it'd be wrong. All stat_items are by definition wrong after a 'stats reset'. - Those that depend on increment/decrement will be wrong until the program exits, and - those that are set to absolute values will be wrong up until the next value is set. That could be seconds or hours later, depending. Related: SYS#5542 Change-Id: If2134768b1076e7af189276c45f2a09a4944303e |
||
|---|---|---|
| .. | ||
| Makefile.am | ||
| buffer.c | ||
| command.c | ||
| cpu_sched_vty.c | ||
| fsm_vty.c | ||
| logging_vty.c | ||
| stats_vty.c | ||
| talloc_ctx_vty.c | ||
| tdef_vty.c | ||
| telnet_interface.c | ||
| utils.c | ||
| vector.c | ||
| vty.c | ||