The MatsBrokerMonitor sends messages on "mats.MatsBrokerMonitor.broadcastUpdate" continuously throughout the day.
This kinda destroys "overview heatmaps" in Grafana, as there will always be a "background noise" for this endpoint.
It should be possible to silence this counting - as it is with logging.
One could argue that this should be a different setting compared to the silencing of logs.
I cannot really see any other usage for such silencing except for such "every 15. seconds" type logging.
Compared to the MatsEagerCache's use of this, it serves a different need: This is noisy since all listening clients will emit lots of loglines upon update which doesn't give any value - the specific logging from the cache itself is much better. (also, the logging do output one logline per 15 minutes or so).
The MatsBrokerMonitor sends messages on "mats.MatsBrokerMonitor.broadcastUpdate" continuously throughout the day. This kinda destroys "overview heatmaps" in Grafana, as there will always be a "background noise" for this endpoint. It should be possible to silence this counting - as it is with logging. One could argue that this should be a different setting compared to the silencing of logs. I cannot really see any other usage for such silencing except for such "every 15. seconds" type logging.
Compared to the MatsEagerCache's use of this, it serves a different need: This is noisy since all listening clients will emit lots of loglines upon update which doesn't give any value - the specific logging from the cache itself is much better. (also, the logging do output one logline per 15 minutes or so).