Massively Multi-Instance: Building and Deploying Microsoft System Center Operations Manager Management Packs in the Ente

1. MGT308 Massively Multi-Instance: Building and Deploying Microsoft System Center Operations Manager Management Packs in the Enterprise Alec King Director, Product Management Veeam Software Corporation

2. Agenda{Placeholder for witty subtitle} • MP good & bad behavior • MP design principles • MP Best Practices – • Packaging and deployment • Discovery and data collection • Alerting and automation • Demo - Good versus Bad Practice • Scalability Danger Signs

3. Management Pack behaviorThe Good, the Bad - and the Buggly • Management Packs can be Good…. • Well designed Health Model • Low-impact operation • Add Value! • Management Packs can be Bad…. • Poorly designed Health Model • High-impact operation • Add Pain!

4. Management Pack design principlesIt’s more Art than Science • Take some time to plan • Consider the end-user • Understand their Requirements • ActionableAlerts – not spam • Knowledge Base – not guesswork • Automation– Yes! But stay in control

5. Management Pack Best PracticesBest practice makes perfect • Packaging • Seal your MP • Break MP into separate files: • Library • Discovery • Monitoring • Reporting

6. Management Pack Best PracticesBest practice makes perfect • Discovery • Avoid Discovery Thrashing • Do not schedule discoveries too frequently • No dynamic properties • Streamline your topology • Workflows = (monitors + rules) x instances

7. Management Pack Best PracticesBest practice makes perfect • Data collection • Make it low-impact • Consider collection scheduling • Consider database impact • Use Optimized Performance Collection • Use Cookdown

8. Optimized Performance Collection • Back

9. NOT Cookdown WMI Perf Collect • <Rule ID=“MyNOTCookdownWMIPerformanceRule" Enabled="true" Target="VMware!nworks.VMware.VEM.VMGUEST" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100"> • <Category>PerformanceCollection</Category> • <DataSources> • <DataSource ID="DS" TypeID="Windows!Microsoft.Windows.WmiPerfCounterProvider"> • <NameSpace>root\nworks</NameSpace> • <Query>select cpuUsedPct from VMSTATS where ID = $Target/Property[Type="VMware!nworks.VMware.VEM.VMGUEST"]/id$’ • </Query> • <Frequency>300</Frequency> • <ObjectName>VMGuest-cpu</ObjectName> • <CounterName>cpuUsedPct</CounterName> • <InstanceName>_Total</InstanceName> • <Value>$Data/Property[@Name=‘cpuUsedPct']$</Value> • </DataSource> • </DataSources> • <WriteActions> • <WriteAction ID="WriteToDB" TypeID="SC!Microsoft.SystemCenter.CollectPerformanceData" /> • <WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData" /> • </WriteActions> • </Rule> • Next

10. Cookdown WMI Data Source Module • <DataSourceModuleType ID="nworks.VMware.VEM.VMSTATS.WMIProvider" Accessibility="Internal" Batching="false"> • <Configuration> • <xsd:element name="NameSpace" type="xsd:string" /> • <xsd:element name="Query" type="xsd:string" /> • <xsd:element name="Frequency" type="xsd:integer" /> • <xsd:element name="ObjectName" type="xsd:string" /> • <xsd:element name="CounterName" type="xsd:string" /> • <xsd:element name="InstanceName" type="xsd:string" /> • <xsd:element name="Value" type="xsd:string" /> • <xsd:element name="EntityIdTarget" type="xsd:string" /> • </Configuration> • <ModuleImplementation Isolation="Any"> • <Composite> • <MemberModules> • <DataSource ID="DS" TypeID="Windows!Microsoft.Windows.WmiProvider"> • <NameSpace>$Config/NameSpace$</NameSpace> • <Query>$Config/Query$</Query> • <Frequency>$Config/Frequency$</Frequency> • </DataSource> • <ConditionDetection ID="Filter" TypeID="System!System.ExpressionFilter"> • <Expression> • <SimpleExpression> <ValueExpression><XPathQuery Type="String">Property[@Name='Id']</XPathQuery> </ValueExpression> • <Operator>Equal</Operator> • <ValueExpression><Value Type="String">$Config/IdTarget$</Value> </ValueExpression> • </SimpleExpression> • </Expression> • </ConditionDetection> • <ConditionDetection ID="Mapper" TypeID="Perf!System.Performance.DataGenericMapper"> • <ObjectName>$Config/ObjectName$</ObjectName> • <CounterName>$Config/CounterName$</CounterName> • <InstanceName>$Config/InstanceName$</InstanceName> • <Value>$Config/Value$</Value> • </ConditionDetection> • </MemberModules> • <Composition> <Node ID="Mapper"> <Node ID="Filter"> <Node ID="DS" /> </Node> </Node> </Composition> • </Composite> • </ModuleImplementation> • <OutputType>Perf!System.Performance.Data</OutputType> • </DataSourceModuleType> • Next

11. Cookdown WMI Perf Collect Rule • <Rule ID="nworks.VMware.VEM.VMGUEST.Collect.cpuUsedPct" Enabled="true" Target="nworks.VMware.VEM.VMGUEST" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100"> • <Category>PerformanceCollection</Category> • <DataSources> • <DataSource ID="DS" TypeID="nworks.VMware.VEM.VMSTATS.WMIProvider"> • <NameSpace>root\nworks</NameSpace> • <Query>select * from VMGUESTSTATS</Query> • <Frequency>300</Frequency> • <ObjectName>VMGuest-cpu</ObjectName> • <CounterName>cpuUsedPct</CounterName> • <InstanceName>_Total</InstanceName> • <Value>$Data/Property[@Name='cpuUsedPct']$</Value> • <IdTarget>$Target/Property[Type="nworks.VMware.VEM.VMGUEST"]/id$</IdTarget> • </DataSource> • </DataSources> • <WriteActions> • <WriteAction ID="WriteToDB" TypeID="SC!Microsoft.SystemCenter.CollectPerformanceData" /> • <WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData" /> • </WriteActions> • </Rule> • Next

12. Cookdown WMI Perf Unit Monitor • <UnitMonitor ID="nworks.VMware.VEM.VMGUEST.Monitor.cpuUsedPct" Accessibility="Internal" Enabled="true" Target="nworks.VMware.VEM.VMGUEST" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="nworks.VMware.VEM.VMSTATS.WmiPerformance.ThresholdMonitorType" ConfirmDelivery="false"> • <Category>Custom</Category> • <AlertSettingsAlertMessage="nworks.VMware.VEM.VMGUEST.Monitor.cpuUsedPct_AlertMessageResourceID"> • <AlertOnState>Error</AlertOnState> • <AutoResolve>true</AutoResolve> • <AlertPriority>Normal</AlertPriority> • <AlertSeverity>MatchMonitorHealth</AlertSeverity> • <AlertParameters> • <AlertParameter1>$Target/Host/Property[Type="System!System.Entity"]/DisplayName$</AlertParameter1> • <AlertParameter2>$Target/Host/Property[Type="nworks.VMware.VEM.VMGUEST"]/host$</AlertParameter2> • <AlertParameter3>$Data/Context/Value$</AlertParameter3> • </AlertParameters> • </AlertSettings> • <OperationalStates> • <OperationalState ID="nworks.VMware.VEM.VMGUEST.Monitor.cpuUsedPct.UnderThreshold" MonitorTypeStateID="UnderThreshold" HealthState="Success" /> • <OperationalState ID="nworks.VMware.VEM.VMGUEST.Monitor.cpuUsedPct.OverThreshold" MonitorTypeStateID="OverThreshold" HealthState="Error" /> • </OperationalStates> • <Configuration> • <NameSpace>root\nworks</NameSpace> • <Query>select * from VMGUESTSTATS</Query> • <Frequency>300</Frequency> • <ObjectName>VMGuest-cpu</ObjectName> • <CounterName>cpuUsedPct</CounterName> • <InstanceName>_Total</InstanceName> • <Value>$Data/Property[@Name='cpuUsedPct']$</Value> • <Threshold>95</Threshold> • <IdTarget>$Target/Property[Type="nworks.VMware.VEM.VMGUEST"]/id$</IdTarget> • </Configuration> • </UnitMonitor> • Next

13. CookdownIf you can’t stand the heat… • Beware ‘external’ data calls • WMI, Scripts, etc • Instances x workflows -> overload source • Cookdown moves the data filter into OM • Same output – but less stress on source

14. Management Pack Best PracticesBest practice makes perfect • Alerting • Make alerts actionable • Consider severity and priority • The never-ending “Roll-up Debate” • Allow flexibility through overrides • Include Knowledge Base • Again - Include Knowledge Base!

15. A Management Scenario & DemoMay the Demo Gods be kind…. • Application ‘X’ must be monitored • Runs as a Windows Service • Add Value! • Ask discovery questions – find the real requirements & pains • Issue: App writes files to a Temp folder - and does not clean up…. • So – also monitor Temp folder for growth • Introduce some automation! • Ops Mgr can not only monitor the temp folder – it can clean it

16. demo MPs - The Good, and the Bad Alec King Director, Product Management Veeam Software

17. Scalability Danger SignsThe Devil is in the Details • Dropping instance data • Event 4506 • Provider module lag • Event 26017 • Agent restart • Event 6024 • Version store (cache) overflow • Event 623 • Long config commit times • Events 21025 & 1210

18. Massively Multi-InstanceAll your scalability are belong to us • Agent • # workflows, discoveries, + disk cache • Management Server / RMS • All agent points above! • Group updates • DB backend performance • Useful link – • Troubleshooting gray agent states (KB 2288515)

19. announcing FREE Report Toolkit!Veeam Extended Generic Report Library Visit http://www.veeam.com/vmware-microsoft-esx-monitoring/resources.html

20. announcing FREE Veeam Backup!VeeamZIP your VMs Visit http://www.veeam.com/virtual-machine-backup-solution-free.html

21. Resources Learning TechNet • Connect. Share. Discuss. • Microsoft Certification & Training Resources http://northamerica.msteched.com www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers • http://microsoft.com/technet http://microsoft.com/msdn

22. Required Slide Complete an evaluation on CommNet and enter to win!

23. MS Tag Scan the Tag to evaluate this session now on myTechEd Mobile

24. © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.