Zabbix APC Battery Replace Date Wrong

[cfuess]

I am fairly new to Zabbix so please bear with me. I have a Smart-UPS SRT 5000 using the "APC Smart-UPS SRT 5000 by SNMP" template that seems to be pulling data in correctly except for "1.2: Battery estimated replace date" showing value of 01/01/2000. This is not a date anywhere in the APC. I found another post that show the below solution but I can not for the life of me figure out where to make this change assuming it will fix my issue. Let me know if there is any other information necessary to get this fixed. Also on version 7.0.0 if that has any bearing on the issue.

"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"

[vsergione]

What is the exact value which is being read from the battery? You can check this if you go to the respective monitoring item and check for latest data

[cfuess]

Hopefully one of the below image has the information you are looking for. I'm not sure if you are looking for the "Current bit set: 0000000000000000" or "Last Value 01/01/2020."

[Markku]

So we are talking about this item prototype:



1.3.6.1.4.1.318.1.1.1.2.3.10.2.1.8.{#SNMPINDEX}

and the only preprocessing rule is discard unchanged. So that OID contains the date as string.

Markku

[cyber]

upsHighPrecBatteryPackCartridgeReplaceDate and upsHighPrecBatteryPackCartridgeHealth are 2 different OID-s... (...2.1.8 and ...2.1.7 respectively...). One returns health bitmap, other one date... So you cannot really use regex from bitmap to apply to date...
I suppose if that date returns some obscure value from year 2020, it might be some default value and not set to something meaningful. So basically useless...

[[email protected]]

Anyone able to sort this out? we're seeing the same and trying to sort it out. we have additional external batteries, so we are seeing on 1.2 and 3.2

upsHighPrecBatteryPackCartridgeHealth.1.1.1	1000000000000000	OctetString
upsHighPrecBatteryPackCartridgeHealth.1.1.2	0000000000000000	OctetString
upsHighPrecBatteryPackCartridgeHealth.2.1.1	1000000000000000	OctetString
upsHighPrecBatteryPackCartridgeHealth.2.1.2	1000000000000000	OctetString
upsHighPrecBatteryPackCartridgeHealth.3.1.1	1000000000000000	OctetString
upsHighPrecBatteryPackCartridgeHealth.3.1.2	0000000000000000	OctetString

upsHighPrecBatteryPackCartridgeReplaceDate.1.1.1	06/07/2026	OctetString
upsHighPrecBatteryPackCartridgeReplaceDate.1.1.2	01/01/2000	OctetString
upsHighPrecBatteryPackCartridgeReplaceDate.2.1.1	06/07/2026	OctetString
upsHighPrecBatteryPackCartridgeReplaceDate.2.1.2	06/07/2026	OctetString
upsHighPrecBatteryPackCartridgeReplaceDate.3.1.1	06/07/2026	OctetString
upsHighPrecBatteryPackCartridgeReplaceDate.3.1.2	06/07/2026	OctetString

upsHighPrecBatteryPackCartridgeInstallDate.1.1.1	07/04/2020	OctetString
upsHighPrecBatteryPackCartridgeInstallDate.1.1.2	01/01/2000	OctetString
upsHighPrecBatteryPackCartridgeInstallDate.2.1.1	12/07/2021	OctetString
upsHighPrecBatteryPackCartridgeInstallDate.2.1.2	12/07/2021	OctetString
upsHighPrecBatteryPackCartridgeInstallDate.3.1.1	12/07/2021	OctetString
upsHighPrecBatteryPackCartridgeInstallDate.3.1.2	12/07/2021	OctetString

upsHighPrecBatteryPackCartridgeStatus.1.1.1	0000000000000000	OctetString
upsHighPrecBatteryPackCartridgeStatus.1.1.2	0000000000000000	OctetString
upsHighPrecBatteryPackCartridgeStatus.2.1.1	0000000000000000	OctetString
upsHighPrecBatteryPackCartridgeStatus.2.1.2	0000000000000000	OctetString
upsHighPrecBatteryPackCartridgeStatus.3.1.1	0000000000000000	OctetString
upsHighPrecBatteryPackCartridgeStatus.3.1.2	0000000000000000	OctetString

Thanks in advance to anyone who can advise on this.