I think NPM or any other monitoring tools couldn't know your profile setting configured by your ISP (but I know one application for wireless broadband that could somehow know your profile settings which is MDMA)
Unless your interface to your ISP experiences "clipping" during your peak hour then that's the only time you may have a hint that your ISP is throttling your bandwidth.
Thanks for the feedback, fortunately we have gone through the effort to request the configured profiles for all of the circuits that we monitor. We've added those values to Orion NPM as part of the custom bandwidth settings. Right now, the only time that we can tell if there is a constrained bandwidth scenario is if we get a response time alert and we check the graphs and see the circuit capped at less than 100%.
Hmm -- that makes me think that an alert that triggers for possible bandwidth throttling for response time where the utilization for either upload or download is less than 100% might help us react in real-time. This might only work for upload traffic though as upload bandwidth tends to have a large constraint (ie dropping ICMP packets) than download traffic in our environment. (Mostly SMB circuits)
I'll have to investigate that possibility.
Has anyone played with any of the tools from the Google collaboration called M-Lab?
A few of their tools can be run from command-line instead of a Java window. Command-line means automation, but it's the delivery of the results and assessing them against pre-set thresholds that are still making me scratch my head a little.