What is the metric used (in percent) that causes the error counters to go from black to red?
Rick
If you go to the Settings Page -> Network Performance Monitor Thresholds, under here you will see the value for Error and Warning for Interface Errors and Discards
Shouldn't these be a percentage of the actual data being processed over the interface instead of a an absolute numerical value? Carrier's use a percent value in their SLA. I can't tell if they are within SLA parameters if I can't set the value to match the provider.
Since NPM already collects the packets/bytes processed and the errors encountered, can percentage be added as an option for the error levels? A count of 1,000 errors in a 1,000,000 packets is much different than 1,000 errors in 1,000 packets, but both show up as the same today.
Do I need to submit this as a new feature request?
We have taken this as a feature request.Thank you for bringing this up.
What, if anything, has been done on this? I am now looking at a similar issue.
We are approaching the one year anniversary of this request. Are we even on the list for inclusion in a future release?
We are going on over 3 years since this simple request was made. What is the status? Our need has not gone away.
When will we see this implemented?
We haven't released the feature yet and unfortunately can't commit to timelines for future features.
I hadn't seen this before so I'm glad you brought it up again. I think it is obvious that this value should be percent based not a static number. We are tracking this as FB379498 and I've just adjusted the priority.
Offhand, do you know if the packet count for an interface includes errored and discarded packets?
We have also been waiting years for this. I can see it has been talked about for some time and I did notice the percent error stat appear in perfstack. Looking at the last post in this idea link it looks like there is something in SQWL. Now to get it into an alert...
