Discussion thread for official Zabbix Template APC UPS

[AlexL]

This thread is designed to provide grounds for discussion of the official Zabbix Template for APC UPS .
The template and details of the template will soon be available in GIT repository.

Zabbix is always looking for ways to improve our services and to make our users happier.
We pride ourselves on doing our best each and every day, but we know that there is always something more to learn.
We would like to hear back from you to know what have you liked and what would you improve in the template.

[reedacus25]

I recently saw that this template was created, and then subsequently broken into more individualized templates.

I think it would be a really great idea to extend this/a template to include APC UPS(s) over local USB interface, rather than just over SNMP.

It will require some dependencies to be met, such as apcupsd being installed, but I have a feeling there are lots of these smaller, local UPS(s) installed that could be monitored as well.

Seems to me this is pretty low-hanging fruit that can apply to a lot of people with minimal effort, especially if monitoring APC UPSs is something Zabbix wants to provide templates for.

[max.ch.88]

I think it would be a really great idea to extend this/a template to include APC UPS(s) over local USB interface, rather than just over SNMP.

It will require some dependencies to be met, such as apcupsd being installed, but I have a feeling there are lots of these smaller, local UPS(s) installed that could be monitored as well.

Sorry, but Zabbix won't make such a template because it uses a non-industrial third-party solution.

[provels]

I use Multimon on a Zabbix Hyper-V VM to monitor the USB APC installed on the virtual host, but it was something I installed quite some time ago. The host runs the Windows version of APCUPSD. Pretty sure I installed the APCUPSD package and Multimon on Zabbix, but I may have killed those brain cells since I did it... Then I made a screen in Zabbix to view it.

[reedacus25]

I can certainly understand not wanting to build an out of the box template that requires extra drivers to work, but this already occurs with ODBC drivers for some database templates.
I've been using my own template that I made to fill this need for myself here, but I imagine that there are plenty of people who would love an out of the box option they could use as well.

[tedkuban]

I have added an environment temperature alert trigger to the SNMP SRT 5000 APC Smart-UPS SRT and SNMP SRT 8000 APC Smart-UPS templates. And I have a problem - my new UPS SRT6KRMXLI has a built-in battery and 2 external battery modules, when connecting the APC Smart-UPS SRT 5000 template, it finds 6 pieces, and collects from them this data:

1.1: Battery estimated replace date 2021-06-23 13:00:50 16.12.2025 Application: Status History
1.1: Battery pack cartridge health 2021-06-23 12:01:51 1000000000000000 Application: Status History
1.2: Battery estimated replace date 2021-06-23 13:00:50 01.01.2000 Application: Status History
1.2: Battery pack cartridge health 2021-06-23 12:01:51 0000000000000000 Application: Status History
2.1: Battery estimated replace date 2021-06-23 13:00:50 16.12.2025 Application: Status History
2.1: Battery pack cartridge health 2021-06-23 12:01:51 1000000000000000 Application: Status History
2.2: Battery estimated replace date 2021-06-23 13:00:50 16.12.2025 Application: Status History
2.2: Battery pack cartridge health 2021-06-23 12:01:51 1000000000000000 Application: Status History
3.1: Battery estimated replace date 2021-06-23 13:00:51 16.12.2025 Application: Status History
3.1: Battery pack cartridge health 2021-06-23 12:01:51 1000000000000000 Application: Status History
3.2: Battery estimated replace date 2021-06-23 13:00:51 16.12.2025 Application: Status History
3.2: Battery pack cartridge health 2021-06-23 12:01:51 0000000000000000 Application: Status History
External battery packs count 2021-06-23 12:00:50 3

In this case, 2 problems are triggered:
3.2: Battery lifetime is not okay
1.2: Battery lifetime is not okay

[jefg]

I have added an environment temperature alert trigger to the SNMP SRT 5000 APC Smart-UPS SRT and SNMP SRT 8000 APC Smart-UPS templates. And I have a problem - my new UPS SRT6KRMXLI has a built-in battery and 2 external battery modules, when connecting the APC Smart-UPS SRT 5000 template, it finds 6 pieces, and collects from them this data:

1.1: Battery estimated replace date 2021-06-23 13:00:50 16.12.2025 Application: Status History
1.1: Battery pack cartridge health 2021-06-23 12:01:51 1000000000000000 Application: Status History
1.2: Battery estimated replace date 2021-06-23 13:00:50 01.01.2000 Application: Status History
1.2: Battery pack cartridge health 2021-06-23 12:01:51 0000000000000000 Application: Status History
2.1: Battery estimated replace date 2021-06-23 13:00:50 16.12.2025 Application: Status History
2.1: Battery pack cartridge health 2021-06-23 12:01:51 1000000000000000 Application: Status History
2.2: Battery estimated replace date 2021-06-23 13:00:50 16.12.2025 Application: Status History
2.2: Battery pack cartridge health 2021-06-23 12:01:51 1000000000000000 Application: Status History
3.1: Battery estimated replace date 2021-06-23 13:00:51 16.12.2025 Application: Status History
3.1: Battery pack cartridge health 2021-06-23 12:01:51 1000000000000000 Application: Status History
3.2: Battery estimated replace date 2021-06-23 13:00:51 16.12.2025 Application: Status History
3.2: Battery pack cartridge health 2021-06-23 12:01:51 0000000000000000 Application: Status History
External battery packs count 2021-06-23 12:00:50 3

In this case, 2 problems are triggered:
3.2: Battery lifetime is not okay
1.2: Battery lifetime is not okay

looks like the regex is not correct for the discovered battery packs:
.regexp("^(0{16})$")}=1
the alert should only fire if one of the 16 bits is 1: 0000000000000000

[jefg]

Another issue I notice with this template
The items that are set to be polled every minute are only polled about every 5 hours.

Some items are fetched according to the set interval eg. input voltage.

tried snmpwalk on the specific OID from the proxy, this returns the value every time requested.

when I delete the item added to the template and add it manually, the polling works according to the set interval.

[johndoe2374]

Another issue I notice with this template
The items that are set to be polled every minute are only polled about every 5 hours.

Some items are fetched according to the set interval eg. input voltage.

tried snmpwalk on the specific OID from the proxy, this returns the value every time requested.

when I delete the item added to the template and add it manually, the polling works according to the set interval.

There's preprocessing in items, they do not save data that hasn't changed during 6 hours of 1 minute interval polling. Here's an example of APC's graph of current:


If you see they're polled every 5 hours instead of 1 minute, it means they don't change during that period. You can just remove preprocessing and it should store every result being requested that corresponds to your polling interval.

[jefg]

looks like the regex is not correct for the discovered battery packs:
.regexp("^(0{16})$")}=1
the alert should only fire if one of the 16 bits is 1: 0000000000000000

fixed it by change the regex to ^0, this makes sure the regex is fired if the first bit is not 1 which means the battery is unhealthy
update since 5.4 the official zabbix template includes regex ^(0)[0|1]{15}$
see https://www.zabbix.com/integrations/..._3000_xlm_snmp


snmpwalk shows a healthy battery returns this
SNMPv2-SMI::enterprises.318.1.1.1.2.3.10.2.1.7.1.1.1 = STRING: "1000000000000000"

The battery cartridge health.
bit 0 Battery lifetime okay
bit 1 Battery lifetime near end, order replacement cartridge
bit 2 Battery lifetime exceeded, replace battery
bit 3 Battery lifetime near end acknowledged, order replacement cartridge
bit 4 Battery lifetime exceeded acknowledged, replace battery
bit 5 Battery measured lifetime near end, order replacement cartridge
bit 6 Battery measured lifetime near end acknowledged, order replacement cartridge

[[email protected]]

Are you saying that the expression should read like this: "regexp","^(0)[0|1]{15}$")=0

[dkplayer]

There's preprocessing in items, they do not save data that hasn't changed during 6 hours of 1 minute interval polling. Here's an example of APC's graph of current:


If you see they're polled every 5 hours instead of 1 minute, it means they don't change during that period. You can just remove preprocessing and it should store every result being requested that corresponds to your polling interval.

Is there any way to make the graphs continuous? Without gaps.

[dkplayer]

Is there any way to make the graphs continuous? Without gaps.

Found a solution on my own. Use the Graph widget with the "Missing data" - "Connected" option enabled. Maybe someone will be useful.

[rsaeks]

I've been using this template for a bit and it seems some of the alerts / triggers are sticky and don't update with the current value. For example the Unacceptable Input Frequency and Unacceptable Input Voltage notifications are still active even though since a power outage everything has returned to normal values. When testing either value on the host and viewing the current data, it is within the acceptable range but the trigger is still acive.

Has anyone made an adjustment to the template to have the trigger update based on the current data?

[fagervan]

I've been using this template for a bit and it seems some of the alerts / triggers are sticky and don't update with the current value. For example the Unacceptable Input Frequency and Unacceptable Input Voltage notifications are still active even though since a power outage everything has returned to normal values. When testing either value on the host and viewing the current data, it is within the acceptable range but the trigger is still acive.

Has anyone made an adjustment to the template to have the trigger update based on the current data?

the template is wrong. In the items,
where it says "Discard unchanged with heartbeat" 6h
you have to change it to "2m"

[jhboricua]

Question. I see that all the Macros for the various APC templates assume a 220-240v output with 50hz frequency, even on units that are 120v only like the SmartUPS 2200 RM.

{$UPS.INPUT_FREQ.MIN.WARN} --> Minimum input frequency for trigger expression. --> 49.7
{$UPS.INPUT_FREQ.MAX.WARN} --> Maximum input frequency for trigger expression. --> 50.3
{$UPS.INPUT_VOLT.MIN.WARN} --> Minimum input voltage for trigger expression. --> 197
{$UPS.INPUT_VOLT.MAX.WARN} --> Maximum input voltage for trigger expression. --> 243

Can someone suggest what would be the equivalent sane values of these macros for an APC 120V 60Hz unit?

[Hamardaban]

These are the threshold values of the metric, beyond which a trigger will be triggered and a "problem" will be generated. If you do not have strict requirements defined by the standards, then you are free to define these values yourself whatever you want. For example, 59,8 - 60,2 Hz \ 110 - 130V