Hi,
I would like to be informed if I will have too many errors on one of the links. If I can be more clear, I would like to know if the level of errors would be higher than 2% in relation to the whole amount of packets on this link.
Since the couple of months I m testing such a trigger:
({host:interface.errors.in.avg(#2)}>(0.02*{host:in terface.totalpackets.in.avg(#2)}) & ({host:interface.totalpackets.in.avg(#2)})>100) | ({host:interface.errors.in.avg(5400)}>(0.02* {host:interface.totalpackets.in.avg(5400)}) & ({host:interface.totalpackets.in.avg(5400)})>1)
It has a two conditions:
1. if i will get a big amount of errors in short amount of time
2. if errors would appear in a small amount but constantly for the longer time
Do you think it is correct? Maybe you have a different method to achive that?
I would like to be informed if I will have too many errors on one of the links. If I can be more clear, I would like to know if the level of errors would be higher than 2% in relation to the whole amount of packets on this link.
Since the couple of months I m testing such a trigger:
({host:interface.errors.in.avg(#2)}>(0.02*{host:in terface.totalpackets.in.avg(#2)}) & ({host:interface.totalpackets.in.avg(#2)})>100) | ({host:interface.errors.in.avg(5400)}>(0.02* {host:interface.totalpackets.in.avg(5400)}) & ({host:interface.totalpackets.in.avg(5400)})>1)
It has a two conditions:
1. if i will get a big amount of errors in short amount of time
2. if errors would appear in a small amount but constantly for the longer time
Do you think it is correct? Maybe you have a different method to achive that?