If some value is discarded during trottling, then why not calculate it to zabbix? For example, zabbix knows that some value has not changed for 1 hour, which means that avg/min/max(/host/somedata,10m) or else can also be easily calculated.
-
-
And your point is? Sorry, you really need to elaborate a bit more here, what you need or what you miss. -
Same thing with graphs
Why Zabbix draws dots on the graph when throttling is used? You have to realise, "discarded" value means completely dropped by Zabbix. It has absolutely no record that it was there. This even affects trend calculation. Imagine at the beginning of an hour you received 1 and at the end you received 10 with throttling. The trend will be 5, while actually it should have been 1.1XXX . Sad, but true. If you need those averages and proper trends I'd recommend avoiding throttling and using data compression on the DB engine level instead, to save disk space.Last edited by dimir; 02-02-2024, 12:45.Comment
-
This just results in that last booster never throttling down (all the way?), and just ramming itself into the upper stages. I don't even get a print out of the throttle value (I had to use telnet in order to see that the print command never happens). My guess is that this script is only seeing what I have locked the throttle to, and not what the throttle actually is. So far all I have found is calculations that are based on maxthrust(no actual thrust either?) and gravity to calculate a user throttle variable that is used to feed into the lock throttle command. I also found a thrust value that is calculated based on a user throttle variable and maxthrust. Where is the actual physical throttle value at?
Comment
-
Comment