The SQL monitors needs to show you the actual amount that the specific threshold was exceeded by. Just having it say that so and so threshold was exceeded without saying by what amount is extremely annoying and makes it impossible to tweak the thesholds to your specific environment. What may be high for one person may be normal for another.
This is not the first time I've encounter a similar issue. The external process doesn't tell you what the return value was either. You guys really need to review all your monitors and make sure that they aren't vague. If you are checking against values/thresholds and a monitor fails, you need to report what the failing value was.
Hi Adrian - thank you for this suggestion - we have had a few requests for it and we're tracking it for a future release. Internal users - it's TT#128.