Management Pack Best Practices Analyzer

• Cookdown Analyzer: Understanding “Green” issues
• Cookdown Analyzer: Understanding Key Property Use in Cookdown
• Cookdown Analyzer: Understanding Non-Key Property Use in Cookdown
• Cookdown Analyzer: How to Solve Cookdown-Related Performance Issues
• Cookdown Analyzer: Understanding $Target/ID$ Use in Cookdown
• Cookdown Analyzer: Understanding Cookdown
• Best Practice: Alerts should have a name and description field
• Best Practice: Alerts should not use hardcoded name and description
• Best Practice: Alerts should reference existing parameters
• Best Practice: Alerts should use correct XPath constructs
• Best Practice: Monitors should eventually roll-up to a standard aggregate monitor
• Best Practice: Management Pack Elements should have display strings
• Best Practice: MP scripts should compile
• Best Practice: Workflows should use the correct scheduler module
• Best Practice: Discoveries should have discovery types
• Best Practice: Discoveries should not be too frequent
• Best Practice: MP Display names should not contain underscores
• Best Practice: Event Collection rules should be categorized correctly
• Best Practice: Event expressions should not compare event descriptions with hard-coded strings
• Best Practice: Expression Type must be explicitly defined for 'more' or 'less' comparisons
• Best Practice: Data type mismatched: Expression types do not correspond to their values
• Best Practice: Unit monitor AlertSeverity should match the unhealthy state used in 2-state unit monitors
• Best Practice: Unit monitor AlertOnState should correspond to an unhealthy state used in 2-state unit monitors
• Best Practice: Knowledge article should have sections in the correct order
• Best Practice: Knowledge article sections should have valid section names
• Best Practice: Knowledge Articles should contain the required sections
• Best Practice: Linked reports should contain filters
• Best Practice: Monitors should have Public accessibility
• Best Practice: Monitors should roll up to classes with Public accessibility
• Best Practice: MP should not reference the Backward Compatibility MP
• Best Practice: Management pack elements should have knowledge articles
• Best Practice: Management Pack Elements should have display descriptions
• Best Practice: MP Elements should not have repeated display names
• Best Practice: MP file sizes should not be too large
• Best Practice: Classes with custom icons should have 16x16 and 80x80 icons
• Best Practice: Rules and monitors should be documented if they are not enabled by default
• Best Practice: Performance Collection rules should be categorized correctly
• Best Practice: Performance Collection should not be too frequent
• Best Practice: Script timeout should be 300 seconds or more
• Best Practice: Each VBScript should have a US locale
• Best Practice: MP should not use self-tuning thresholds
• Best Practice: MP should not use R2 PowerShell module
• Best Practice: Target expressions should be valid
• Best Practice: Unit monitors should have AutoResolve set to true
• Best Practice: Unit monitors should not have manual reset states
• Best Practice: Views should be sorted properly
• Best Practice: Views should define a resolution state
• Best Practice: Workflows should not use WMI queries
• Best Practice: WMI queries should not use “Select *” statements