You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have BBU and not have cachevault.
And not work recovery trigger LSI controller {#CTLID} battery state is {ITEM.LASTVALUE} -
({Template LSI JSON discovery:lsi.ctl.bbustate.["{#CTLID}"].str(Optimal)}=0 and {Template LSI JSON discovery:lsi.ctl.bbustate.["{#CTLID}"].strlen()}>0) or ({Template LSI JSON discovery:lsi.ctl.cvstate.["{#CTLID}"].str(Optimal)}=0 and {Template LSI JSON discovery:lsi.ctl.cvstate.["{#CTLID}"].strlen()}>0)
because key lsi.ctl.cvdata.["0"] has status Not supported with error "Status" : "Failure"
and trigger expression lsi.ctl.cvstate.["{#CTLID}"].strlen()}>0 causes an error Cannot evaluate expression: "Cannot evaluate function "SERVER:lsi.ctl.cvstate.["0"].strlen()": not enough data.".
Same errors with triggers:
LSI controller {#CTLID} battery was replaced
LSI controller {#CTLID} battery is need to be replaced
Zabbix server 4.2.3
The text was updated successfully, but these errors were encountered:
I have BBU and not have cachevault.
And not work recovery trigger LSI controller {#CTLID} battery state is {ITEM.LASTVALUE} -
({Template LSI JSON discovery:lsi.ctl.bbustate.["{#CTLID}"].str(Optimal)}=0 and {Template LSI JSON discovery:lsi.ctl.bbustate.["{#CTLID}"].strlen()}>0) or ({Template LSI JSON discovery:lsi.ctl.cvstate.["{#CTLID}"].str(Optimal)}=0 and {Template LSI JSON discovery:lsi.ctl.cvstate.["{#CTLID}"].strlen()}>0)
because key lsi.ctl.cvdata.["0"] has status Not supported with error "Status" : "Failure"
and trigger expression lsi.ctl.cvstate.["{#CTLID}"].strlen()}>0 causes an error
Cannot evaluate expression: "Cannot evaluate function "SERVER:lsi.ctl.cvstate.["0"].strlen()": not enough data.".
Same errors with triggers:
LSI controller {#CTLID} battery was replaced
LSI controller {#CTLID} battery is need to be replaced
Zabbix server 4.2.3
The text was updated successfully, but these errors were encountered: