OpsMgr 2012 end-to-end monitoring
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

OpsMgr 2012 end-to-end monitoring

  • 2,683 views
Uploaded on

How do I successfully monitor my services end-to-end with OpsMgr 2012

How do I successfully monitor my services end-to-end with OpsMgr 2012

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
2,683
On Slideshare
2,678
From Embeds
5
Number of Embeds
2

Actions

Shares
Downloads
71
Comments
0
Likes
0

Embeds 5

http://www.linkedin.com 4
https://www.linkedin.com 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. “How do I successfully monitor my services end-to-end with OpsMgr 2012”Walter EikenboomPrincipal consultant INOVATIV
  • 2. AGENDARequirements  What is a LOB application  Selecting your business apps (IT Business alignment)  Gathering informationPrerequisites  IT Maturity  Operational processes (PPT)  Collecting technical informationDesign for monitoring  Components  Relations  Events and triggerBuild  Component monitoring  Distributed applications  End user experience
  • 3. What is a LOB application LOB application  Components  Windows OS  Forefront TMG  Processing services  Virtual machines  SQL server  Azure database  IIS  VMM  Component relations  Perspective Stock trader LOB
  • 4. Selecting your business appsAll Applications in the IT service catalog! Why: A LOB application in the service map is mapped to:  Business processes  Business functions  Business capabilitiesAnd that’s why they provide value to your business!The Business/IT Alignment focuses on the following processes:  Define an IT service strategy  Identify and map services  Identify IT service demand and manage business requests  Develop and evaluate the IT service portfolio  Manage service levels
  • 5. App ControllerApp Controller• Self-service Application Management Across Private and Public Clouds• Easy Deployment and Operations for Your Application Services Through a Highly Intuitive Service-centric Interface• Visibility and Control with Unified Console Across Private and Public Cloud Resources and Applications
  • 6. Gathering informationGathering information Description Business service (LOB) application name Stock Trader Web based stock trading and processing application for end Functional description internal and external users Business owner Dieter Wijckmans Business s service CI CI0012345 Number of users/ Number of Affected users 275 internal/ 450 external New or existing services Existing sinds June 2010 Service owner Oskar Landman Technical owner Walter Eikenboom Priority High Availability Business hours Alert notification 24x7 Available in OTA OA SLA 99,0% Policy considerations SOX, SAS 70
  • 7. AGENDARequirements  What is a LOB application  Selecting your business apps (IT Business alignment)  Gathering informationPrerequisites  IT Maturity  OpsMgr 2012  Monitoring ambition  Collecting technical informationDesign for monitoring  Components  Relations  Events and triggerBuild  Component monitoring  Distributed applications  End user experience
  • 8. IT MaturityMonitoring level ready for LOB monitoring People Process Technology
  • 9. OpsMgr 2012
  • 10. Monitoring ambition End User Experience(Console, Web, SharePoint) (Synthetic Transactions) Consistent UX Application Monitoring (.NET, J2E) Infrastructure Monitoring (OS, SQL, IIS) Infrastructure Monitoring (Fabric)
  • 11. Extending the platform
  • 12. Vicinity dashboard
  • 13. AGENDARequirements  What is a LOB application  Selecting your business apps (IT Business alignment)  Gathering informationPrerequisites  IT Maturity  OpsMgr 2012  Monitoring ambition  Collecting technical informationDesign for monitoring  Events and trigger  Components  Relations  Events and triggerBuild  Component monitoring  Distributed applications  End user experience
  • 14. Monitoring components Define ComponentDatabase SQL 2008 DB 001SQL cluster Instance ATMG Array b web publishingIIS on StocktraderwebService BSL on StocktraderBSL Processing service  Identify events  rules Performance counters  Triggers Response times Define monitoring requirements based on SLA, OLA and UC
  • 15. Demo
  • 16. Prerequisites Define Component relations Stocktraderweb <-> Database X, Y and AAB StocktraderSQL <-> Azure DB StocktraderSQL <-> Stocktraderweb IIS Identify application discovery items Define Groups  . Security  Overrides  Views  Targets  Reports Define monitoring requirements based on SLA, OLA and UC
  • 17. SLA and OLA: how do they relateService level agreement (SLA). A written Woodgroveagreement documenting required levels of Business usersservice. The SLA is agreed upon by theservice provider and the consumer, or by Service Levelthe service provider and a partner provider. Agreement (SLA)SLAs should list the metrics and measuresthat define success for both the serviceprovider and the consumer. Desktop Service Manager End to end Desktop ServiceOperating level agreement (OLA). An Operating Levelagreement between one or more internal Agreement (OLA)teams that supports the requirements setforth in the SLAs.Underpinning contract (UC). A legally Network team Active Directory team Security teambinding contract in place of or in addition toan SLA. This type of contract is with apartner service provider responsible for Network Hardware Vendor Underpinningbuilding service deliverables for the SLA. Contract (UC)
  • 18. MOF 4.0
  • 19. MOF 4: Operate phaseThe Operate Phase of the IT service lifecycle represents the culmination of the two phasesthat precede it. The Operate Phase focuses on what to do after the services are in place.After an IT service has been successfully deployed, ensuring that it operates to meetbusiness needs and expectations becomes the top priority. This is the focus of the OperatePhase, which depends on four primary endeavors:• Effective ongoing management of the service• Proactive and ongoing monitoring of its health• Effective and readily available help to assist with use of the service• Restoration of a service to health when things go wrong
  • 20. Service monitoring and controlGoals of Service Monitoring and ControlService Monitoring and Control (SMC) is the real-time observation of and alerting abouthealth conditions (characteristics that indicate success or failure) in an IT environment. Ithelps to ensure that deployed services are operated, maintained, and supported in line withthe service level agreement (SLA) targets agreed to between the business and IT.The components required to successfully implement Monitoring and Control are: • Establishing a service monitoring function. • Understanding the nature of new and existing IT services. • Understanding the requirements for successful service monitoring tools. • Ensuring that all relevant information from service monitoring is acted upon by the appropriate people. • Generating all the information required by other SMFs. • Improving the quality of service information.
  • 21. DEMO
  • 22. Thanks!Bio: Walter EikenboomAs a principal consultant Walter is specialized ininfrastructure optimization where automationand simplifying operations is one of his keystrengths by overviewing people, process andtechnology to manage the most complexinfrastructures. Innovation and pre-salesconsultant on Microsoft System Center, privateCloud en workspace optimization with a vision indesigns. Walter provides workshops andpresentations on proactive and automatinginfrastructure management, moving to a newplatform or solution. Walter loves to talk withcustomers on how the world is changing andhow IT should adapt to stay aligned with yourbusiness. Follow me on Twitter @wwwally orcontact me walter.eikenboom@inovativ.nl tostay in touch.