In NPM 2024.1.0, the Interface Errors & Discards widgets allow you to click on the error count. When you do, you are taken to Custom Chart - Interface Chart. When you adjust the time frame and click on a point in time when the errors occur, it confirms the identity of the interface but that's all. It would be helpful of you could somehow drill down to see what conversation was associated with the errors being generated. In our case, when we execute the Cisco "show interface counters errors" command, we can see input errors and oversize errors. Input errors are usually an L1 problem, but we have changed jumpers, transceivers, etc. and it does not appear to have an L1 cause. We suspect it's application related or possibly the need for VLAN pruning in our switch uplinks. Network Performance Monitor, however, currently is not much help in troubleshooting interface errors. It is great that it lets us know interface errors are occurring, but you must rely on other tools and techniques to find the source of the errors. I opened Case #01606358. The engineer said NPM currently does not do what I need it to do. He suggested I post a feature request.Viola! Here it is. I hope this makes sense. Thank you.
