Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Do the built in APM templates take care of time unit conversion?

Hello,

Do the built in APM templates take care of time unit conversion? I've noticed perfmon counters that report average times in say, ms, but the built in warning/critical thresholds in the APM templates appear to be seconds. Is something in APM doing that conversion already, or are the templates just using the wrong default thresholds? I didn't see anything obvious, but figured I'd ask.

I've seen this a couple times before, but one particular counter I've noticed this on recently is the Exchange 2010 Mailbox Role Counters (advanced), Average Document Indexing time. The perfmon counter appears to report back in ms, but the documentation reports that the value shouldn't be above 30 seconds. The APM template is set to warning value of 20 and critical value of 40, while the actual value being reported back to APM still appears to be the value in ms.

Find more posts tagged with

Accepted answers

All comments

aLTeReGo

The built in warning and critical thresholds in APM are based on the statistic returned from the counter. If the statistic collected is the number "10", what ten means is dependent upon the counter being monitored. In your case this may be 10 milliseconds.

As for the Exchange 2010 Mailbox Role Counters template, this counter returns a statistic value in milliseconds, and the threshold should not exceed 30 seconds, which is represented in the critical statistic threshold setting of "30000.00".

30,000 milliseconds = 30 seconds.

vedichymn

Weird, mine were set to 20 & 40 respectively, but we're still on 4.02, so maybe that's something that's since been fixed. I overrode those and things worked properly, just wanted to make sure there wasn't something I was missing.

vedichymn

In particular, here's what I saw, but like I said, might be fixed in 4.2

aLTeReGo

Nice catch. I'll file a bug to have this investigated. In the meantime you can update the Threshold manually in the template. Thanks again for bringing this to our attention.