OPManager Administratively Down Ports

OPManager Administratively Down Ports

We are currently trialing OPManager.
 
I'm a bit confused on the following behaviour. If a switch port on any of our ProCurve gear is Administratively down (meaning we want it disable) OPManager logs a Critical Event for that switch. Yet if a port is Administratively up but the physical link is down it logs a "Trouble" Event.
 
If a port is Administratively disabled, it is likely we want it that way so it shouldn't be logged as a problem. On the flip side, if it is Administratively enabled yet offline there is more chance of it being a real legit problem.
 
Is this behaviour changeable because it is a quite annoying to have my switches showing critical because of this.
 
Thanks

                New to ADSelfService Plus?