UPS monitoring. Part Two - Automating Analytics

Some time ago, I built a system for evaluating the viability of office UPSs. The assessment is based on long-term monitoring. Based on the results of using the system, I finished it and learned a lot of interesting things, which I will tell you about - welcome under cat.

The first part

In general, the idea turned out to be correct. From a one-time request to UPS, you can only find out that life is a pain. Some of the parameters are relevant to reality only without 220 V connected, some, according to the results of the analysis, turn out to be outright nonsense, some need to be recalculated by hand, checking with reality.

Looking ahead, I tried to add these nuances to the system. Well, do not count with your hands, in fact, we are automatists or something.

Here, for example, the parameter "battery percentage". As a single value, it reports nothing and is usually equal to 100. What really matters: how quickly the battery is discharged, how quickly it is charged, how many times it has been discharged to critical values. Surprisingly, the UPS itself does some of this work, however, according to very strange formulas; more on that below.

Parameter "UPS load” is very good and useful. But if you look at it in dynamics, it turns out that sometimes there is nonsense, and sometimes - interesting information about the connected equipment.

Β«Battery voltage". Practically the Grail, if not for one thing: the absolute majority of the time the battery is on charge, and the voltage of the charge, not the battery, is displayed in the parameter. Wait, isn't the self-test routine supposed to do that?..

Β«self-test". It should, only its results are displayed nowhere. If the self-test fails, the UPS will turn off and scream like a cut, this is the only result available. Plus, not all UPSs report the very fact of the self-test that took place.

And "nice try vendor" is the most interesting parameter available "battery runtime". It is designed to predict how long the battery will last under the available load. Also, the internal logic of the behavior of the UPS is tied to it. In fact, it shows pink dreams, especially when fully charged.

There were also nuances of an organizational nature.

For example, all UPSs that came across to me have data on the date of the battery (already two fields). At the same time, I managed to record this data (after replacing the battery, respectively) only in products from APC, and then dancing with a tambourine. In Powercom, this information cannot be pushed in any way, at least under Windows.
The same Powercom distinguished itself by the same values ​​in the "serial number" field. It also cannot be recorded.

Calculation "battery runtimeβ€œ seems to include values ​​from periods when 220V is connected to the UPS, and, accordingly, the battery data is frankly wrong. In fact, the battery runtime can be safely divided by 2, or even by 3. And at the same time, it will still remain a purely synthetic value. In addition, it is based on the "battery load", which also has some oddities: on some instances, it does not reset for a long time after a high load, and on others it tends to zero.

Despite such a zoo, you can see that all parameters are still amenable to some algorithmization. This means that you can not only look at the data (and even more so manually view all the available records), but immediately drive the entire array into the analyzer and build recommendations based on them. Which was implemented in the new version of the software.

The UPS details page will issue warnings and recommendations:

  • logged at least one self-test failure (if the UPS provides this functionality)
  • the need to replace the battery
  • unusual load values ​​on the UPS
  • no battery data
  • unusual input voltage values
  • recommendations for the use of data and maintenance of the UPS

(all possible options can be found in ups_additional.php)
A necessary condition for correct analytics, of course, is the maximum possible data collection.

On the main page, you can immediately see the maximum and critical values ​​and the corrected runtime prediction.

And also:

  • the maximum power loss time is now correctly calculated
  • up-to-date information from the UPS is indicated in green, obsolete in gray, critical in red and orange
  • added database optimization procedure (started manually, with automatic backup creation)
  • removed useless information from the main screen and added useful πŸ™‚

UPS monitoring. Part Two - Automating Analytics

UPS monitoring. Part Two - Automating Analytics

Disclaimer:
Of course, this is not an enterprise at all. Almost all installation is manual. There were not enough tests, in some places errors pop up. Nevertheless, I use it with benefit and wish you.
github.com/automatize-it/NUT_UPS_monitoring_webserver_for_Windows

Thank you for attention!

Only registered users can participate in the survey. Sign in, you are welcome.

Do you need to add something else to the software?

  • finish up the enterprise!

  • setup-s would be nice not to set it by hand

  • no, it's ok

  • gasoline, burn it

  • a bunch of everything you need, write in the comments

34 users voted. 13 users abstained.

Source: habr.com

Add a comment