'm testing 4.2.5 before upgrading our instance. I'm particularly keen on the item throttling and whilst the data collection side of it works exactly like I'd expect then the graphing doesn't seem to work as I envisaged it would.whatsapp web whatsapp plus
In the attached plot at 15:06 I changed the item from every minute to throttling with heartbeat with a heartbeat time of 5m. Whilst i can see the updates on the graph it all looks very disjointed which makes it harder to follow, especially for some other items with multiple items on a graph.
If everything is ok and data comes in every 5 minutes, then eventually it will settle down and show a continuous line, but if the ping returns a 0 at any point then that process will start all over again. Surely there should be a way of detecting if throttling is used and joining points of the heartbeat time or less?
In the attached plot at 15:06 I changed the item from every minute to throttling with heartbeat with a heartbeat time of 5m. Whilst i can see the updates on the graph it all looks very disjointed which makes it harder to follow, especially for some other items with multiple items on a graph.
If everything is ok and data comes in every 5 minutes, then eventually it will settle down and show a continuous line, but if the ping returns a 0 at any point then that process will start all over again. Surely there should be a way of detecting if throttling is used and joining points of the heartbeat time or less?
Comment