The really annoying part for me is monitoring didn't catch this failure, I didn't realize a digital 0 or 1 could have a third option of nodata. I had to update my triggers to account for this with an OR and another check.
Windows; {servernamehere:log.count[C:\Program Files\OpenVPN\log\openvpnstatus.log,^client,ANSI,1 00,all,0].avg(#5)}<0.2 or {servernamehere:log.count[C:\Program
Files\OpenVPN\log\openvpn-status.log,^client,ANSI,100,all,0].nodata(10m)}=1
Linux; {servernamehere:log.count[/var/log/openvpn/openvpn-status.log,"^CLIENT_LIST,client",ANSI,100,all,0].avg(#5)}<0.2 or
{servernamehere:log.count[/var/log/openvpn/openvpn-status.log,"^CLIENT_LIST,client",ANSI,100,all,0].nodata(10m)}=1
Windows; {servernamehere:log.count[C:\Program Files\OpenVPN\log\openvpnstatus.log,^client,ANSI,1 00,all,0].avg(#5)}<0.2 or {servernamehere:log.count[C:\Program
Files\OpenVPN\log\openvpn-status.log,^client,ANSI,100,all,0].nodata(10m)}=1
Linux; {servernamehere:log.count[/var/log/openvpn/openvpn-status.log,"^CLIENT_LIST,client",ANSI,100,all,0].avg(#5)}<0.2 or
{servernamehere:log.count[/var/log/openvpn/openvpn-status.log,"^CLIENT_LIST,client",ANSI,100,all,0].nodata(10m)}=1
Comment