Exporteren (0) Afdrukken
Alles uitvouwen
EN
Deze inhoud is niet beschikbaar in uw taal, maar wel in het Engels.

Guide for System Center Management Pack for Workflow Manager 1.0

Updated: October 17, 2012

This guide was written based on version 1.0.0.0 of the Management Pack for Microsoft Workflow Manager.

Supported Configurations

This Management pack requires System Center Operations Manager 2007 R2 or later. A dedicated Operations Manager management group is not required.

The following table details the supported configurations for the Management Pack for Microsoft Workflow Manager.

 

Configuration

Support

Microsoft Workflow Manager

1.0

System Center Operations Manager 2007 R2

Not tested

System Center Operations Manager 2012

Tested

Management pack scope

This Management pack supports monitoring of the Workflow Farms.

Prerequisites

The following Management Packs must be imported into System Center Operation Manager (SCOM) before Microsoft Workflow Manager Management Pack.

  1. SQL Server 2012 Management Pack 6.3.173.0 or later.

  2. Microsoft Service Bus Management Pack 1.0.0.0 or later.

Mandatory Configuration

  • Import prerequisite Management Packs.

  • Enable the Agent Proxy setting on all agents that are installed on servers participating in a Workflow Farm. For instructions, see the procedure that follows this list.

To enable the Agent Proxy setting

  1. Open the Operations Console and click the Administration button.

  2. In the Administrator pane, click Agent Managed.

  3. Double-click an agent in the list.

  4. On the Security tab, select Allow this agent to act as a proxy and discover managed objects on other computers.

Files in this management pack

The Management Pack for Microsoft Workflow Manager includes the following files:

  • Microsoft.Workflow.Manager.MP

Management Pack Purpose

In this section:

  1. Management Scenarios

  2. How Health Rolls Up

For details on the discoveries, rules, monitors, and views in this Management pack, see Appendix: Management Pack Contents.

Monitoring Scenarios

Discovery of Roles, Hosts, Host Groups and Farms

The following objects are automatically discovered:

  • Farms Group

  • Farm

  • Nodes Group

  • Node

  • Back End Role, Front End Role monitors

  • Management Databases

 

Monitoring scenario Description

Associated rules and monitors

Availability monitoring

This scenario checks the availability of the objects.

  • Workflow Manager Backend Role Availability Monitor: Availability monitor for Workflow backend role. It can be in two states, and can generate an alert with no auto-resolve.

  • Workflow Manager Frontend Role Availability Monitor: Availability monitor for Workflow frontend role. It can be in two states, and can generate an alert with no auto-resolve.

Performance health monitor

This scenario checks performance health based on monitoring particular events.

  • Frequent Service Bus Errors Reported monitor: Performance monitor for Workflow error #368 (Failed Service Bus Operation). It can be in two states, and can generate an alert with no auto-resolve.

  • Workflow Manager Service has fail-fast/unhandled exceptions reported too frequently monitor: Performance monitor Workflow error #1 (Trace Unhandled Exception), #10 (App Domain Unhandled Exception) and #19 (Trace Fail Fast). It can be in two states, and can generate an alert with no auto-resolve. This section uses the Fail-fast/Unhandled Exception reported rules (three rules).

  • Workflow Manager Backend service has started too frequently monitor: Performance monitor for Workflow services, monitoring of event #288 (Backend Started) and #582 (Management Service Started). It can be in two states, and can generate an alert with no auto-resolve. This section uses the Workflow Backend Startup Failed rule.

Monitoring of performance counters

This scenario checks performance health based on monitoring of the particular performance counters.

  • Workflow Manager Backend Thread Count monitor: Performance monitor for Workflow backend threads count. It can be in two states, can generate alert with auto resolve. This section uses the Workflow Manager Backend thread count performance rule.

  • Workflow Manager Frontend Thread Count monitor: Performance monitor for Workflow frontend threads count. It can be in two states, can generate alert with auto resolve. This section uses the Workflow Manager Frontend thread count performance rule.

Performance collection rules

This scenario displays the monitoring collection of the particular entities.

This section uses the following rules:

  • Workflow Manager Requests Failed per second Performance Rule

  • Workflow Manager Requests Processed per second Performance Rule

  • Workflow Manager Episodes Completed Performance Rule

How Health Rolls Up

The following diagram shows how the health states of objects roll up in this management pack.

Workflow Manager Health States

The following diagram provides extended details about health rollup between specific management pack classes. Use it to learn more about specific entities of management pack and health relations between them.

Workflow Manager Health Rollup Extended Details

Configuring the Management Pack for Microsoft Workflow Manager

This section provides guidance on configuring and tuning this management pack.

Best Practice: Create a Management Pack for Customizations

By default, Operations Manager saves all customizations such as overrides to the Default Management Pack. As a best practice, you should instead create a separate management pack for each sealed management pack you want to customize.

When you create a management pack for the purpose of storing customized settings for a sealed management pack, it is helpful to base the name of the new management pack on the name of the management pack that it is customizing, such as “Microsoft Workflow Manager Customizations”.

Creating a new management pack for storing customizations of each sealed management pack makes it easier to export the customizations from a test environment to a production environment. It also makes it easier to delete a management pack, because you must delete any dependencies before you can delete a management pack. If customizations for all management packs are saved in the Default Management Pack and you need to delete a single management pack, you must first delete the Default Management Pack, which also deletes customizations to other management packs.

RunAs Profiles

When the Management Pack is first imported, it creates a RunAs profile:

  • WorkflowManager Discovery and Monitoring Profile: This profile is associated with all discoveries, all monitors and tasks.

By default, all discoveries, monitors, and tasks defined in the management pack default to using the accounts defined in the “Default Action Account” Run As profile. If the default action account for a given system does not have the necessary permissions to discover or monitor the instance of Workflow Manager, then those systems can be bound to more specific credentials in the Workflow Manager Discovery and Monitoring Profile which do have access.

The following steps help you configure Run As profiles for Workflow Manager:

To configure RunAs Profiles

  1. Identify the names of the target computers where the default action account has insufficient rights to monitor Workflow Manager.

  2. For each system, create or use an existing set of credentials that have all privileges.

  3. For each set of credentials identified in step 2, make sure a corresponding Run As account exists in the management group. Create the Run As account if necessary.

  4. Set up the mappings between the targets and the Run As accounts on the Run As Accounts tab of each of the Run As profiles. Use the following table to identify mappings.

     

    RunAs Profile Targets

    Workflow Manager Discovery Account

    Classes:

    1. Workflow Manager DB

    2. Workflow Manager Farm

    3. Workflow Manager Node

    4. Workflow Manager Backend Role

    5. Workflow Manager Frontend Role

    6. Workflow Manager Nodes Group

    For more information, see Run As Profiles and Run As Accounts in Operations Manager 2007.

Optional Configuration

By default, SQL Server monitor for Workflow Manager databases is disabled. If you would like to enable it, you should download and install System Center Management pack for SQL Server beforehand.

Links

The following links connect you to information about common tasks that are associated with System Center Management Packs.

For questions on the Operations Manager and Management Packs, see the System Center Operations Manager Community Forum. A useful resource is the System Center Operations Manager Unleashed blog

ImportantImportant
All information and content on non-Microsoft sites is provided by the owner or the users of the website. Microsoft makes no warranties, express, implied, or statutory, as to the information at this website.

Appendix: Management Pack Contents

The Management Pack for Microsoft Workflow Manager discovers the object types described in the following sections. Not all of the objects are automatically discovered. Use overrides to discover those objects that are not discovered automatically.

Workflow Manager Farms Discovery (Workflow Manager Generic Discovery)

Discovery Information

 

Interval Enabled When to enable

14400

True

N/A

noteNote
If you are using connectors, you can disable the monitor and enable its corresponding rule to enable alerts without changing health status.

Related Views

 

View Description Rules and Monitors that Populate the View

Farms

Display all discovered Farms

Workflow Manager Nodes Discovery (Workflow Manager Generic Discovery)

Discovery Information

 

Interval Enabled When to enable

14400

True

N/A

Related Monitors

 

Monitor Data Source Interval Alert Reset Behavior Corresponding Rule Enabled When to Enable

Workflow Manager Backend Role Availability Monitor

Appropriate Windows Service: Workflow Service Backend

60

True

Automatic

True

N/A

Workflow Manager Frontend Role Availability Monitor

Appropriate Windows Service: Workflow Service Frontend

60

True

Automatic

True

N/A

Workflow Manager Service has fail-fast/unhandled exceptions reported too frequently monitor

Performance counter

1800

True

Automatic

Fail-fast/Unhandled Exception reported rules

True

N/A

Frequent Service Bus Errors Reported monitor

Performance counter

1800

True

Automatic

True

N/A

Workflow Manager Backend service has started too frequently monitor

Performance counter

1800

True

Automatic

Workflow Backend Startup Failed rule

True

N/A

Workflow Instance Appearing to Complete Monitor

Performance counter

300

True

Automatic

Workflow Episodes Completed Per Second Rule

True

N/A

Workflow Manager Nodes Not Processing Messages Monitor

Performance counter

300

True

Automatic

Workflow Requests Processed per second rule

True

N/A

Workflow Manager Requests Failed Monitor

Performance counter

900

True

Automatic

Workflow Requests Failed per second rule

True

N/A

noteNote
If you are using connectors, you can disable the monitor and enable its corresponding rule to enable alerts without changing health status.

Related Views

 

View Description Rules and Monitors that Populate the View

Diagram View

Display all trees of all entities


Workflow Manager 1.0 MSDN Community Forum


Build Date:

2014-01-17

Community-inhoud

Toevoegen
Weergeven:
© 2014 Microsoft