What is the metric used (in percent) that causes the error counters to go from black to red?
Rick
What is the metric used (in percent) that causes the error counters to go from black to red?
Rick
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?
Rick
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?
Thanks for getting this going. All of our SLAs are based on a percentage
count of errors. Having the percent count lets us know at a glance if SLA
is being met.
I don't know what exactly is included in the packet counts and if it
includes the errors /discards.
Rick
On Mon, Oct 27, 2014 at 10:18 AM, cobrien <
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.