tree fa60b01dd5f27527e2cd6d3f1eaee28119881260
parent e90c7176be0f627610b9c28f44551ad19f114672
author Neels Hofmeyr <nhofmeyr@sysmocom.de> 1631648940 +0200
committer neels <nhofmeyr@sysmocom.de> 1633026823 +0000

refactor stat_item: report only changed values

Change the functionality of skipping unchanged values: instead of
looking up whether new values have been set on a stat item, rather
remember the last reported value and skip reporting identical values.

stats_test.c shows that previously, a stat item reported a value of 10
again, even though the previous report had already sent a value of 10.
That's just because the value 10 was explicitly set again, internally.

From a perspective of preserving all data points, it could make sense to
send consecutive identical values. But since we already collapse all
data points per reporting period into a max, that is pointless.

Related: SYS#5542
Change-Id: I8f4cf34dfed17e0879716fa2cbeee137c158978b