rules, rules, rules: proactively automate management of the service infrastructure

12
Rules, Rules, Rules Proactively Automate the Management of the Service Infrastructure Karen Charles Product Manager [email protected] John Woodard Technical Sales Specialist [email protected]

Upload: novell

Post on 10-May-2015

486 views

Category:

Documents


2 download

DESCRIPTION

This session is an introduction to building rules into service models. Rules enable you to manage the definitions of severity and priority and automated actions, such as notifications. These rules also enable you to proactively monitor and manage the service infrastructure in real time. The solution provides more than after-the-fact reporting on technology performance and availability; it provides a view into the current trajectory of service performance and into potential service breaches before they occur. This allows IT to apply the proper resources to the highest priority services as required.The Novell solution also factors in multi-faceted rules and visualization. This allows you to prioritize performance against availability. An example of this would be raising awareness before an event that will affect performance while that service is still available. The Novell solution is a true "service" monitoring and management solution because of its ability to calendar business hours, and because use and demand are also factored in when calculating service awareness and breaches versus pure up/down availability. Finally, the session will discuss and demonstrate how these rules are configured; it will discuss best practices for configuring/defining, and the real-time multi-dimensional visualization of the service via the appropriate dashboards.

TRANSCRIPT

Page 1: Rules, Rules, Rules: Proactively Automate Management of the Service Infrastructure

Rules, Rules, RulesProactively Automate the Managementof the Service Infrastructure

Karen CharlesProduct [email protected]

John WoodardTechnical Sales [email protected]

Page 2: Rules, Rules, Rules: Proactively Automate Management of the Service Infrastructure

© Novell, Inc. All rights reserved.2

Overview

How can we manage the service using Novell® Business Service Level Manager™?

What services do we want to monitor?

What information is important to us?

How can we notify staff when our services fail?

Page 3: Rules, Rules, Rules: Proactively Automate Management of the Service Infrastructure

© Novell, Inc. All rights reserved.3

Novell® Data Center Solutions

Page 4: Rules, Rules, Rules: Proactively Automate Management of the Service Infrastructure

© Novell, Inc. All rights reserved.4

Data CenterBusiness Service ManagementBusiness Service Management – Enables IT to

provide a service view of the infrastructure aligned to

the business measuring real-time operations, while

providing control over the infrastructure.

Operating Controlling

Page 5: Rules, Rules, Rules: Proactively Automate Management of the Service Infrastructure

© Novell, Inc. All rights reserved.5

Data Center Business Service Management/Overview - How Does it Work?

Trans ValueTrans Volume

End-to-End Management Configuration Management

Inte

grat

eVi

sual

ize

Mod

el a

nd A

naly

ze

Federation

Java-basedClient

Browser BasedWeb 2.0Dashboards

Novell® BusinessService Manager™

End-to-end Management Configuration Management

Novell BusinessCMDB360™

Novell BusinessService Level Manager™

NovellmyCMDB™

Intelligent Service Model

Generated Revenue Transaction VolumeInventory

Business Metrics

Data Center

Web Services

Data Base

LANOrder Processing

ManagementTechnology

Performance Management Problem Virtual Data Release Configuration 3rd Party CMDB

Trans Value Discovery Open Source Incident Change Asset Metrics Facility Trans Volume

Page 6: Rules, Rules, Rules: Proactively Automate Management of the Service Infrastructure

© Novell, Inc. All rights reserved.6

Business Service Level ManagerTM

• Fully automated real-time and historical analytics

• Complete integration of both technology and business service metrics

• Real-time dashboard analytics and reporting

• Flexibility to choose any service, component, or metric as the basis for a Service Level Agreement

Page 7: Rules, Rules, Rules: Proactively Automate Management of the Service Infrastructure

© Novell, Inc. All rights reserved.7

Storing Key Metric Data

• Input data:– Send in raw data– Send in key metric data– Use element condition data

• Objective type:– Availability

> Calculated using element condition> Can use general availability, child availability, or a customized availability

– Calculation > Calculated using an alarm property> Key metric can be a calculated percentage based on match criteria, sum,

average, minimum, maximum, or the property value

Page 8: Rules, Rules, Rules: Proactively Automate Management of the Service Infrastructure

© Novell, Inc. All rights reserved.8

Controlling Element Condition Data

• Use algorithms to calculate the element condition– Default shows highest severity of child element– Algorithm library:

> Average> Lowest> Different variations that can be customized

– Custom algorithm actions:> Gather elements> Eliminate elements> Simple calculations (highest, average, lowest)> Fire a script

• Algorithm tracer

Page 9: Rules, Rules, Rules: Proactively Automate Management of the Service Infrastructure

© Novell, Inc. All rights reserved.9

Using Automations to Notify

Triggers:

– Alarm opened or closed

– Element condition change

– Service level breach

Actions:

– Play a computer sound

– Send an e-mail

– Pop-up a message

– Run a script

Page 10: Rules, Rules, Rules: Proactively Automate Management of the Service Infrastructure

© Novell, Inc. All rights reserved.10

Let's Put It All Together

Demonstration

Questions and Answers

Page 11: Rules, Rules, Rules: Proactively Automate Management of the Service Infrastructure
Page 12: Rules, Rules, Rules: Proactively Automate Management of the Service Infrastructure

Unpublished Work of Novell, Inc. All Rights Reserved.This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.

General DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for Novell products remains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.