1. Service Models in SCOM with VSAE examples
Jonathan Almquist
Nathan Foreman
#MMSSCOM
MMS Minnesota 2014

2. Session Overview What is a service model in SCOM? Why is it important?
Design considerations and pitfalls
Example service model
Create the sample service model using VSAE
MMS Minnesota 2014

3. Key Takeaways Identify components that require state
Implement models that support cookdown
Provide monitoring targets that make sense
Enable more effective management of the system
MMS Minnesota 2014

4. What is a Service Model? Object-Oriented
Classes, types, objects, relationships
Representation of an application (façade)
Instances are discovered
Monitors target discovered instances
MMS Minnesota 2014

5. Why is it Important? Unit monitor targeting
Health Explorer readability
No more empty white circles
Implementing 3rd party tools
Bluestripe > SCOM > Live Maps
Notifications, views, reporting, etc.
MMS Minnesota 2014

6. Design Considerations
What are the different roles that make up the application?
Correlate to classes and types
Which base class to use?
Local Application (rollup inherited)
Application Component (rollup not inherited)
Computer Role (rollup inherited, bonus state view)
Are there any components that should have a health state?
Logical disk is an example
Any useful properties that can be discovered?
We can use these values in monitoring workflows
How are these components related?
How are we going to discover all these things?
MMS Minnesota 2014

7. Design Pitfalls Too complex or too many classes
Volatile objects or properties
Should be relatively static
Discoveries run too frequently
Especially for volatile properties
Script-based discoveries targeting broad classes
MMS Minnesota 2014

8. Service Model Example Tool and Die Application Classes Design Server
Queue Server
Plant Controller
Plant machine
Plant Queue
Design Server
(Computer Role)
Queue Server
(Computer Role)
Plant Controller
(Computer Role)
Plant Machine
(Computer Role)
Plant Queue
(App Component)
MMS Minnesota 2014

9. Service Model Example
Separating components into a distributed application
Tool and Die distributed application
Corporate
Plants
Tool and Die
(System Service)
Corporate
(System Group)
Plants
(System Group)
Design Server
(Computer Role)
Queue Server
(Computer Role)
Plant Controller
(Computer Role)
Plant Machine
(Computer Role)
Plant Queue
(App Component)
MMS Minnesota 2014

10. Demo
Create the sample service model using VSAE
MMS Minnesota 2014

11. Creating an Application Service Model in Operations Manager
Jonathan Almquist, Nathan Foreman
#MMSSCOM