{"id":37047,"date":"2019-10-31T22:15:29","date_gmt":"2019-10-31T19:15:29","guid":{"rendered":"https:\/\/prohoster.info\/blog\/monitoring-ibp-chast-vtoraya-avtomatiziruem-analitiku\/"},"modified":"2019-10-31T22:15:29","modified_gmt":"2019-10-31T19:15:29","slug":"monitoring-ibp-chast-vtoraya-avtomatiziruem-analitiku","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/monitoring-ibp-chast-vtoraya-avtomatiziruem-analitiku","title":{"rendered":"UPS Monitoring. Part Two \u2013 Automating Analytics","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Some time ago, I developed a system to evaluate the viability of office UPS units. The evaluation is based on long-term monitoring. As a result of my findings, I refined the system and learned a lot of interesting things, which I will share \u2013 welcome to the details.
\n<\/a><\/noindex>
\nThe first part<\/a><\/noindex><\/p>\n

Overall, the concept turned out to be correct. From a one-time request to the UPS, you can only learn that life is pain. Some parameters are only relevant when 220 V is disconnected, others turn out to be outright nonsense based on my analysis, and some need to be recalculated manually, cross-checking with reality.<\/p>\n

Looking ahead, I tried to incorporate these nuances into the system. After all, we are automators and not just counting by hand.<\/p>\n

For example, the parameter «battery charge in percent<\/b>« as a single value conveys nothing and is usually equal to 100. What really matters is how quickly the battery discharges, how quickly it charges, and how many times it has been discharged to critical levels. Surprisingly, part of this work is done by the UPS itself, but based on very strange formulas; more on that below.<\/p>\n

The parameter «load on the UPS<\/b>» is quite good and useful. But if you look at it dynamically, it turns out that sometimes it makes no sense, and at other times it provides interesting information about the connected equipment. <\/p>\n

<<Battery voltage<\/b>« is practically the Holy Grail, if it weren't for one thing: the vast majority of the time, the battery is on charge, and the parameter displays the charging voltage rather than the battery voltage. Wait, shouldn't this be handled by the self-test procedure? ..<\/p>\n

<<Self-test<\/b>« should, but its results are not displayed anywhere. If the self-test fails, the UPS will shut down and scream like crazy; this is the only available result. Plus, not all UPS systems report the fact that the self-test occurred.<\/p>\n

And \"nice try vendor\" \u2013 the most interesting of the available parameters is «battery runtime<\/b>«. It is designed to predict how long the battery will last under the current load. Internal logic of the UPS is also tied to it. In fact, it shows rosy dreams, especially when fully charged.<\/p>\n

There are also organizational nuances to consider. <\/p>\n

For example, all the UPS devices I've encountered have information about the battery date (two fields, in fact). However, I could only record this data (after replacing the battery, of course) for products from APC, and even then it was a hassle. In Powercom, there's simply no way to input this information, at least not under Windows.
\nThe same Powercom distinguished itself with identical values in the 'serial number' field. It does not allow for any record. <\/p>\n

The calculation of «battery runtime<\/b>« apparently includes values from the periods when 220 V is connected to the UPS, and therefore, the battery data is openly inaccurate. In fact, the battery runtime can safely be divided by 2, or even by 3. And even then, it will still remain a purely synthetic value. Moreover, it is based on \"battery load\", which also exhibits oddities: on some units, it takes a long time to reset after a high load, while on others, it tends towards zero.<\/p>\n

Despite such a mix, it is evident that all parameters are still subject to some form of algorithmization. Thus, it is possible not just to view the data (and certainly not to manually sift through all the existing records), but to input the entire array into an analyzer and base recommendations on them. This has been implemented in the new version of the software.<\/p>\n

The UPS information page will issue warnings and recommendations:<\/p>\n