{"id":116,"date":"2008-10-16T19:25:00","date_gmt":"2008-10-16T19:25:00","guid":{"rendered":"http:\/\/joapen.com\/blog\/2008\/10\/16\/the-top-ten-misconceptions-for-performance-and-availability-monitoring\/"},"modified":"2008-10-16T19:25:00","modified_gmt":"2008-10-16T19:25:00","slug":"the-top-ten-misconceptions-for-performance-and-availability-monitoring","status":"publish","type":"post","link":"http:\/\/joapen.com\/blog\/2008\/10\/16\/the-top-ten-misconceptions-for-performance-and-availability-monitoring\/","title":{"rendered":"The Top Ten Misconceptions for Performance and Availability Monitoring"},"content":{"rendered":"

\"\"<\/a><\/p>\n

Great Article to review concepts -> Link<\/a><\/p>\n

<\/p>\n

    <\/p>\n
  1. You only need real or syntethic user monitoring<\/li>\n
  2. You can model your environment manually.<\/li>\n
  3. Monitoring software needs to reside in house.<\/li>\n
  4. The Configuration Management database (CMDB) is a single physical repository of all knowledge.<\/li>\n
  5. A Company’s infrastructure monitoring strategy can operate in its own detached silo. You need to be integrated to the business needs.<\/li>\n
  6. Second or sub-second sampling rates are always necessary. <\/li>\n
  7. Monitoring all the available metrics for a system or application is the best approach. Performance problems follow the Pareto’s rule: 80% of the problems are caused by 20% of the components of a system\/application.<\/li>\n
  8. All Systems in the IT enterprise will be monitored.<\/li>\n
  9. Monitoring processes or services for an application suffices. It’s necessary to focus also on services interaction.<\/li>\n
  10. Monitoring basic Infrastructure is enough. Architecture & Application are the main causes of performance problems.<\/li>\n<\/ol>\n

    Ok, this kind of reminds are very useful but I always have problems when I have to convince a customer spending some time reviewing performance problems that are not clear or they are in the background. What this kind of things happens I always try to:<\/p>\n