Making Managed Availability Easier to Monitor and Troublesh - PowerPoint Presentation

Slide1
Slide2

Making Managed Availability Easier to Monitor and Troubleshoot

Jay Cotton, Stephen McComas, Ben Winzenz

BRK3163Slide3

Session Objectives

Attendees will leave this break out session with an understanding of how to monitor and troubleshoot Exchange 2013 Managed Availability by using the Managed Availability TroubleshooterSlide4

Managed Availability (Quick Review)Slide5

Managed Availability (Quick Review)

Managed

Availability works by implementing Probes, Monitors and Responders:

The

Probe

is the component that performs the simple test. It doesn’t care whether the test passes or fails. It simply performs the test.

The

Monitor

consumes the results of the Probe, and uses that to determine the Health state of the item being monitored.

Depending on the Health state, one or more graduated

Responder

actions may be invoked. All of this information is logged in the Crimson event channel under Active Monitoring, or Managed Availability. Slide6

Event Logging

Managed Availability makes extensive use of crimson channel event logMicrosoft-Exchange-ActiveMonitoring

ProbeDefinition

ProbeResult

MonitorDefinition

MonitorResult

ResponderDefinition

ResponderResult

Microsoft-Exchange-

ManagedAvailability

Monitoring

RecoveryActionResultsSlide7

Managed Availability Event Logging

All Managed Availability items are logged in the Crimson Channel Logs.

Microsoft-Exchange-

ActiveMonitoring

ProbeDefinition

ProbeResult

MonitorDefinition

MonitorResult

ResponderDefinition

ResponderResult

Microsoft-Exchange-

ManagedAvailabilityMonitoringRecoveryActionResultsManaged Availability log files can be found on the Exchange server: C:\Windows\System32\winevt\LogsSlide8

Managed Availability Components

Probes

Monitors

Responders

DefinitionsSlide9

Probes

Measure the user’s perception of the service

Typically synthetic user

transactionsSlide10

Probes

A successful Probe has a Result Type of 3A failed Probe has a Result Type of 4 or 5Slide11

Monitors

Consumes the Results of Probes

Sets the Health State of the various components based on Probe Results

Can trigger Escalations, or RespondersSlide12

Responders :

Executes a response to alert generated by a monitor

Responders

Restart – Terminates and restarts service

Reset

AppPool

– Cycles IIS application pool

Failover – Initiates a database or server failover

Bugcheck

– Initiates a

bugcheck

of the serverOffline – Takes a protocol on a machine out of serviceOnline – Places a machine back into serviceEscalate – Escalates an issue to an adminSlide13

Definitions

Probe, monitor and responder definitions initialized and logged when Health Manager worker process starts.All Probes, Monitors, and responders have a definition. This dictates what they are testing (Probes) and how they will respond (Monitors and Responders)Slide14

Recovery

Actions:Managed availability logs all recovery actions to the crimson channel

Microsoft.Exchange.ManagedAvailability

/

RecoveryActions

Event 500 indicates that a recovery action was started

Event 501 indicates that a recovery action was successful

Event 502 indicates that a recovery action was unsuccessfulSlide15

Managed Availability – Recovery Actions

Useful properties for Recovery Action event

Id - Action that was taken. Common values are

RestartService

,

RecycleApplicationPool

,

ComponentOffline

, or

ServerFailover

State - Whether the action has started (event 500) or finished (event 501/502)

ResourceName - The object that was affected by the action. This will be the name of a service for RestartService actions, or the name of a server for server-level actionsEndTime - The time the action completedResult - Whether the action succeeded or notRequestorName - The name of the Responder that took the actionSlide16
Slide17

Troubleshooting MethodologySlide18

How do I troubleshoot Managed Availability?

Hint: Work backwards

Get-

HealthReport

and Get-

ServerHealth

(Current snapshot)

Review Current Managed Availability Logging

Investigate Managed Availability Recovery Actions Results

Correlate Recovery Action Results to the appropriate Probe

Review the Probe failures to determine next stepsSlide19

Managed Availability TroubleshooterSlide20

Managed Availability Troubleshooter

Components:

PowerShell URI Text Box

Server Drop Down Menu

Health Report

Server Health Report

Local Active Monitoring

Critical Events

Test Type

(Outlook, OWA

ect

..)Work Item (Probe, Responder, Monitor)Max Results Returned (Default 101)Definitions (Probes, Monitors, Responders)Date Time PickerTroubleshooting Tips LinkSlide21

Managed Availability Troubleshooter

Common Components:

Server Drop Down Menu

: Builds a list of all Exchange 2013 servers in the Org

Health Report

: Displays a Health Report of the server picked in the dropdown menu

Server Health:

Displays the results of all

montiors

and their current health state

Max Results Returned:

If selected returns the number of results based on the value that is chosen. (Defaults to 101)Date Time Picker: If selected results are displayed from this time rangeTroubleshooting Tips: Link to TechNet for useful troubleshooting tips for a particular Health SetSlide22

Managed Availability Troubleshooter

Test Types:

Local Active Monitoring:

Choosing this option enables a dropdown menu of Health Sets that you can now run tests on. These results are comprised of the below:

Probes

Monitors

Responders

When we have chosen which results to review, click on Get Results to display a Grid View of resultsSlide23

Managed Availability Troubleshooter

Test Types:

Critical Events:

Choosing this option enables a dropdown menu of

Critical System Events that you can review.

The events that can be reviewed can be seen on the right.

When you have selected the events you wish review, simply click the “Get Results” button.

The results are displayed in a grid view.Slide24

Troubleshooting Methodology

Using the Managed Availability TroubleshooterSlide25

Methodology Applied with the Managed Availability Troubleshooter

Review the

HealthReport

and Server Health (Current snapshot)

Review Current Managed Availability Logging

Investigate Managed Availability Recovery Actions Results

Correlate Recovery Action Results to the appropriate Probe

Review the Probe failures to determine next stepsSlide26

DemoSlide27

Download From Here!

http://

aka.ms/m.a.t.s

o

r @

The Ignite Yammer Group

BRK3163

Questions?Slide28

Pre-Release

Programs

Be first

in line

!

Exchange & SharePoint On-Premises Programs

Customers

get:

Early access to new features

Opportunity to shape features

Close relationship with the product teams

Opportunity to provide feedbackTechnical conference calls with members of the product teamsOpportunity to review and comment on documentationGet selected to be in a program:Sign-up at Ignite at the Preview Program deskORFill out a nomination: http://aka.ms/joinofficeQuestions:Visit the Preview Program desk in the Expo HallContact us at: ignite2015taps@microsoft.com Slide29

Free Resources for DevOps Practices

Optimize your

DevOps practices & tools

:

Get started on your DevOps journey:

aka.ms/

devops

Accelerate your application

delivery lifecycle

Download the Forrester Infrastructure-as-Code whitepaper:

Complexity kills. Automate with Infra as code:

aka.ms/

iac_tlp

Technical resources for Practitioners:

Get access to free online training,

evals

and HOLs:

aka.ms/

devopsmva

Join the Community conversations:

Use

#

TalkDevOps

on Twitter

RSVP

hereSlide30

Visit

Myignite

at

http://myignite.microsoft.com

or download and use the

Ignite

Mobile

App

with

the QR code above.

Please evaluate this session

Your feedback is important to us!Slide31