Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Analyzing performance problems

 

Ops Center Analyzer provides analytical diagnostics to quickly identify, isolate, and determine the root cause of problems.

The traditional approach of troubleshooting performance problems in the unified infrastructure poses several challenges. For example, it can be difficult to identify performance problem in a storage infrastructure environment that includes various virtual machines, servers, network, and storage.

Ops Center Analyzer offers an out-of-the-box analytics solution which lets you identify and troubleshoot performance problems at the node level. The topology view shows the graphical representation of the infrastructure components and their dependencies. This view is crucial for troubleshooting performance problems and helps achieve efficient root cause analysis.

Identifying performance problems

 

The IT infrastructure is becoming more complex each day with rapidly emerging converged infrastructures. Performance problems occur due to various factors in your environment. Identifying the performance problems and troubleshooting the problems quickly is crucial.

As part of your performance management strategy, you define performance goals and criteria for monitoring your environment. The performance problems occur when these predefined goals are not met. Use Ops Center Analyzer advanced troubleshooting features to quickly fix problems.

The following situations indicate a performance problem in your environment:

  • An SLO violation occurs

    Typically, SLAs define the SLOs to evaluate the quality of service. SLO profiles define the threshold values for the performance parameters that you use to evaluate the quality of service. When the threshold values are exceeded, an SLO violation occurs.

  • A sharp deviation from the baseline data occurs

    When no SLOs are defined for your environment, you can use the baseline values to evaluate your system performance. The current performance is compared to the past performance trends, and when there is a significant deviation from the baseline values, Ops Center Analyzer sends an alert to notify you of a potential performance problem so you have enough time to troubleshoot.

  • The customer notifies you of an application performance degradation and slowdown of the infrastructure.

The common causes for performance problems are as follows:

  • Increased load in an otherwise stable operating environment
  • Inefficient load balancing strategy, which might cause underutilization of resources
  • Changes in the system configuration
  • Resource management in a shared infrastructure

Infrastructure components and key performance metrics

 

You must analyze the key performance metrics relevant to the problem and the workload being analyzed.

The components and key performance metrics available in Ops Center Analyzer for monitoring performance are listed in the following tables:

Component Performance problem Key performance metrics
Identify the resources with SLO violations or performance problems Identify the related resources used by the affected resources Identify the resources that might be the root cause
Server CPU contention VM
  • vCPU Ready
  • vCPU usage
ESX
  • pCPU usage
  • Host CPU Ready1
ESX
  • pCPU usage
  • Host CPU Ready1
VM
  • vCPU Ready
  • vCPU usage
Memory swap VM
  • Usage %
  • Active memory
  • Swap in/out rate
ESX
  • Swap in/out rate1
ESX
  • Usage %
  • Active memory1
  • Swap in/out rate1
VM
  • Usage %
  • Active memory
  • Swap in/out rate1
Memory contention VM
  • Balloon
VM
  • Balloon1
ESX
  • Usage %
  • Balloon1
VM
  • Usage %
  • Active memory
  • Balloon
Response time decrement ESX
  • pCPU usage
  • Device Latency (R/W)1
   
Storage Response time decrement VM
  • Latency (R/W)
Hypervisor
  • Latency (T)1
LU (Volume)
  • Response time (R/W/T)
Port
  • usage
Processor
  • MPB utilization1
Cache
  • Write Pending %
  • Side file %
Pool
  • Utilization
Parity Group
  • Utilization %
  • Read Hit %
VM
  • Read (KBps)
  • Write (KBps)
  • Read Operations
  • Write Operations
LU (Volume)
  • IOPS (R/W/T)
Network Error packet VM
  • droppedRx
  • droppedTx
  • Transmitted/received (KBps)
  VM
  • Transmitted/received (KBps)
  • PacketsTx1
  • Packets Rx1
1 The performance metric is available in Analyzer detail view.

Analytics workflow

 

The workflow for analyzing performance problems and identifying the root cause is as follows:

GUID-CDEE3476-2523-45FA-B93F-BFFEB948593C-low.png

Detecting performance problems

 

View the threshold violations using the Dashboard tab and Events tab. You can configure the system to send email notifications when the threshold values are exceeded. You can also use the search feature in the Analytics tab to find the target resources for performance analysis.

Dashboard

The dashboard displays when you log on to Ops Center Analyzer. You can create a custom dashboard, and choose to view the reports of monitored resources.

The dashboard displays summary reports for the monitored resources, system and resource events, event trends, and consumer groups. The report widgets display the threshold violations and critical alerts detected on all monitored resources when threshold values are exceeded.

In the following dashboard view, the warnings display on the monitored VMs and volumes. From the report widgets, click links to access the E2E view and analyze the cause of the threshold violations.

GUID-CDB87A98-1DF9-4F35-B9D9-627DA9A4DFC5-low.png

Events tab

The Events tab displays a list of resource and system events. View the severity of each event, date and time of the occurrence, category, device, and the component name. You can navigate from the Events tab to the E2E view for further analysis.

Email notifications

Ops Center Analyzer allows you to configure email notifications. When the threshold values are exceeded, the system sends an email to notify you of the potential performance problem.

Search

Use the search feature on the Dasboard tab to search for a resource in the Consumers, Servers, Switches, Storage Systems, and Volumes categories. From the returned search results, select the resources to analyze, and launch the E2E view or Sparkline view for further analysis.

Analyzing performance bottlenecks

 

The performance degradation in the user resources is caused by a performance bottleneck on the server, network, or storage components.

An image showing the performance bottleneck on the server, network and storage components.

A performance bottleneck can occur for various reasons, such as CPU contention, inefficient load balancing, applications sharing storage pools, port and parity group utilization in shared infrastructure, cache utilization, changes in dynamic tiering policies, and configuration changes.

Identify and analyze the component causing the bottleneck in any of the following views:

  • E2E view
  • Analyze bottleneck window
  • Sparkline view
  • Detail view

Identifying the bottleneck in E2E view

 

Analyze the configuration of the infrastructure components in the E2E topology view.

The following procedure describes the workflow of tasks for troubleshooting the problem that occurred in a VM component.

Procedure

  1. Navigate to the E2E view in one of the following ways:

    • On the Analytics tab, perform a search for the target resources, and from the returned search results, select the target resource for analysis and click Show E2E View.
    • On the dashboard, the report widgets display the number of affected resources that exceeded the threshold values. For example, the VMs/Host report displays the number of affected VMs, and when you click the number link, a new window displays a list of monitored VMs. Select the resources to analyze and click Show E2E View.
  2. In the E2E View, analyze the server-related and storage-related components to identify the resources causing performance problems.

    • Click Server View box icon representing the server view to get a server-oriented view of the business system configuration. The key components to monitor while analyzing the server performance are:
      • CPU
      • Memory
      • NIC
      • HBA
      • Disk
    • Click Storage View cylinder icon representing the storage view to get a storage-oriented view of the business system configuration. The key components to monitor while analyzing the storage performance are:
      • Port
      • Processor
      • Cache
      • Pool
      • Parity Group
    In the following example, the alert indicators display on the VMs. When you analyze the VMs in the Server View, you can view alerts associated with the CPU server components. The E2E view you can see the alerts for each VM and the CPU associated with        the VMs.
    NoteThe E2E View does not show component information such as CPU, memory, and disk space for Windows and Linux hosts.
  3. To analyze the resource associated with an alert, click the resource icon and select Verify Bottleneck.

    For example, to check whether CPU is the bottleneck candidate, click the CPU icon and select Verify Bottleneck.
  4. The Analyze Bottleneck window displays the performance trend reports of the bottleneck candidate and the resource used as the base point of analysis. If the performance charts display similar trend patterns in the same time period, you can assume that the selected resource is the bottleneck candidate. If not, repeat the analysis for other resources with alerts in the Verify Bottleneck window.

    For example, in the Verify Bottleneck window, the bottleneck candidate (CPU) appears in a graph in the upper pane, and the VM where the problem occurred appears in a graph in the lower pane. The performance charts display similar trend patterns in the same time period, which confirms that the CPU is the bottleneck candidate.

    The Analyze Bottleneck window provides line graphs that help you determine         bottleneck candidates.

  5. You can also use the resource sharing percentage to identify the bottleneck in the shared infrastructure. On the E2E view tool bar, from the Configuration Information menu, select an option that displays the highest resource sharing percentage. Hover over the icons in the E2E view to see the shared percentage of each resource. Resources with a high sharing rate are the potential bottleneck candidates.

    For example, when no alerts display on the dashboard, or in the E2E view, and when you cannot identify the bottleneck candidate using the Analyze Bottleneck window, use the resource sharing percentage to identify the affected resources in the shared infrastructure. Select Configuration Status from the Configuration Information menu, to see information about the drives in the parity group, such as Drive Status and Used Spare Count. This tool is useful for parity groups with flash drives. Click on the Parity Group resource icon from the E2E View and select Show Detail to see details for the SSD Used Endurance Indicator and the FMD Battery Life Indicator.

E2E infrastructure topology view

 

The E2E topology view provides the detailed configuration of the infrastructure resources and lets you view the relationship between the infrastructure components. You can manually analyze the dependencies between the components in your environment and identify the resource causing performance problems. By using the topology maps, you can easily monitor and manage your resources. Use this view to monitor resources in your data center, including applications, virtual machines, servers, networks, and storage systems.

In the E2E view, each node represents a resource, and the connecting links represent the relationship between the infrastructure components. You can analyze a target resource and all associated resources. You can also view alerts associated with all related resources and trace the problem at the root level. The node-based E2E view helps you analyze the problem on the affected node and its impact on other resources. You can also open the Analyzer detail view UI to view a detailed performance report for a selected resource.

Topology view components

The E2E view displays the topology related to the selected resources under the following default infrastructure groups:

 

  • Consumer: The name of the consumer group to which the selected resource belongs and the details about the consumer grade level.
  • Server: The associated server components, such as VMs and hosts.
  • Network: The associated network components, such as switches.
  • Storage: The associated storage components, such as volumes.

A number link is shown next to each resource icon. For example, when you select a storage subsystem as a target resource for analysis, and if 50 volumes belong to this storage subsystem, the value Volumes 50 is shown under the Storage infrastructure group. Click the Volumes link to open the Volumes - Storage window, which displays details about the volumes in the storage subsystem. From the Volumes list, select the priority of volumes that you want to analyze in the E2E view.

E2E view tool bar The tool bar provides quick access to frequently used menu options and icons:
Options Description

Sparkline View

Navigate to the Sparkline view to analyze the performance of the base point resource and the related resources to identify the bottleneck.

Critical

Number of critical alerts in the topology view.

Warning

Number of warnings in the topology view.

Configuration Information

Number of indicators for configuration information.

Configuration Status

Information about drives, such as availability or the battery life of an SSD drive.

Copy Pair Information

Copy pair information for volumes.

VSM Information

Virtual storage machine information for copy pair volumes.

High Share Rate

Resource sharing percentage of a shared resource. Hover over the resource icons to display the share percentage for each resource. Resources with high share rate are potential bottleneck candidates.

The Share Rate value is not displayed when you set a Hypervisor or Storage System as the base point of analysis.

Select OFF to turn off this feature.

Configuration Status

Information about drives, such as availability or the battery life of an SSD drive.

Storage and Server Views

The following topology views are supported:

  • Storage View: Maps the storage-related components, such as ports, processors, cache, pools, and parity groups.
  • Server View: Maps the server-related components, such as CPU, memory, NIC, HBA, and disk.

Lock Highlight

Select a resource node and click Lock Highlight to highlight all related components in the topology view. The resource configuration remains highlighted until you release the lock on the resource node. This feature helps you understand the links between components and analyze the system configuration in detail.

To release the lock, click Lock Highlight again.

Repaint

Select a resource node and click Repaint to move the resource from bottom-to-top or right-to-left to the prime position. Use this option to change the display order of resources.

E2E view menu bar
Menu bar items Menu items and description

Show Detail button

Select a resource and click Show Detail. The performance summary report of the resource opens in a new window. You can also view the events related to the resource in the Events tab.

Show Report in Analyzer detail view

Click a resource icon and select Show Report in Analyzer detail view. The Analyzer detail view UI opens in a separate browser window. The resource tree opens to the selected resource, along with the latest available report in the Performance view.

Analyze Bottleneck menu

Select a resource and click Analyze Bottleneck. The Analyze Bottleneck Summary window opens. From the summary window, you can display the following tabs for the detailed analysis:

  • Verify Bottleneck
  • Identify Affected Resources
  • Analyze Shared Resources
  • Analyze Related Changes
  • Check Recovery Plans

Action menu

  • Change Base Point: Select a resource and click Change Base Point to change the node of analysis. The topology view opens for the selected resource in a new window.
  • Execute Actions: Select a resource and click Execute Actions to run predefined actions on a resource node. The event actions allow you to send notifications to your administrator for troubleshooting performance problems.

Set Flag menu

Select a resource and click Set Flag to flag a resource so you can analyze the flagged resource at a later point. To remove the flag, click Unset Flag.

Show Prediction Select a resource and click Show Prediction to generate a report showing the predicted performance trend for that resource. The report is based on the risk profiles that you select. After the report is generated, go to the Predictive Analytics tab to view the results.

Comparing performance trends in Sparkline view

 

Use the Sparkline view to analyze the health and performance of the resources in your monitoring environment. The Sparkline view displays performance reports for multiple nodes in the same pane for a quick comparison between different nodes. Display detailed performance metrics for each node and find the correlation with other nodes.

The following procedure describes the workflow of tasks for troubleshooting the problem that occurred in a VM component.

Procedure

  1. Navigate to the Sparkline view in one of the following ways:

    • On the Analytics tab, search for the target resources, and from the returned search results, select the target resources for analysis and click Show Sparkline View.
    • From the E2E View, select a resource, and then from the tool bar, click Sparkline View.
  2. In the Sparkline view, analyze and compare the performance trends of the target and related resources. You can select more than one target resource for analysis.

    In the following example, analyze the performance trends of the VM and the associated server components. The VM and CPU display similar trends in the same time period, which confirms that the CPU is the component affecting the performance of the VM.

    The Sparkline View shows line graphs that represent the         performance trends of the selected resources.

    Note

     

    • The Sparkline view does not display the overall performance trends of Hypervisors and Storage Systems. However, you can analyze the performance of all associated components of hypervisors (such as, CPU, Memory, NIC, HBA, Disk) and storage systems (such as, port, processor, cache, pool, parity group) in the sparkline view.
    • You can add a maximum of 20 target resources (base point resources) in the Sparkline view, and display a maximum of 200 graphs.
  3. To analyze data with finer granularity, select the graph, and click Show Performance from the menu.

    The performance window displays trends for the selected components.

Identifying affected resources

 

In the Analyze Bottleneck window, click the Identify affected resources tab. In this window, you can identify the consumers, hosts, VMs, and volumes that use the bottleneck candidate. You can also verify the status of each resource. Based on the severity level displayed, you can troubleshoot the performance problems associated with the resources.

The Identify Affected Resources window includes the resource name, status,             grade, and description.

Analyzing the cause of the bottleneck

 

The root bottleneck cause can be resource contention issues in the shared infrastructure, or configuration changes in the environment.

Analyzing shared resources

 

Performance problems arise when an application or a resource uses most of the available resources in the shared infrastructure. Ops Center Analyzer supports efficient optimization of the shared infrastructure by quickly identifying the resource contention problems.

  1. In the Analyze Bottleneck window, click Analyze Shared Resources.

  2. In the Analyze Shared Resources window, the performance charts appear for the bottleneck candidate and the resources using the bottleneck candidate.

  3. Compare the performance trends of the bottleneck candidate with the resources that use it. If the compared resources display similar trends, then you can assume that the resource in the shared infrastructure is causing the bottleneck.

    If you cannot determine the cause of the bottleneck from the displayed graphs, check the graphs of different metrics. To view the graph of a different metric, select it from the Metric list. You can also add a performance graph of a different component from the Add Graph menu.

    In the following example, the CPU utilization value of a virtual machine is compared with the CPU utilization of other virtual machines and volumes. The performance trends confirm that one of the VMs in the shared infrastructure is overutilizing the CPU. The CPU bottlenecks occur when several VMs run on the same physical machine, and end up sharing the same CPU. If the VMs (logical resources) share the same CPU (physical resource) and if one of the VMs utilizes the CPU more than the others, the total efficiency of the shared resource is degraded and the CPU utilization rate increases. The CPU might become saturated with requests because of resource contention problems.

    A screenshot of the Analyze Shared Resources window.

Analyzing configuration changes

 

Ops Center Analyzer supports the tracking of infrastructure configuration changes. Analyze these changes and correlate them with the performance data to determine the effects of configuration changes on system performance and behavior.

  1. In the Analyze Bottleneck window, click Analyze Related Changes.

  2. In the Analyze Related Changes window, analyze whether the bottleneck is caused by the changes in the system configuration.

    The Analyze Related Changes window displays a combination chart that combines the features of the line and bar chart. The line indicates the performance of the bottleneck candidate and bars indicate the configuration change events. Analyze the change events to see if any of them caused performance variations in the bottleneck candidate.

    The Change Events table in the lower pane displays a list of configuration-related changes and their details. Zoom in on the performance trend chart to select a shorter time period and view the change events that occurred in the selected time range.

    In the following example, the performance data of the bottleneck candidate (CPU) is compared with the change events that occurred in the specified time period. You can correlate the performance data of the CPU and the change events to determine the effects on system performance. Based on the analysis, you can confirm that a lot of configuration change events caused performance degradation in the CPU.

    To print the list of configuration change events, click the Open Print Page button. For a large number of events, the print operation might become unstable. From the Rows / Page pull-down menu, reduce the number of listed events, then retry the print operation.

    A screenshot of the Analyze Related Changes window.

Checking recovery plans

 

Ops Center Analyzer supports generating recovery plans for the processor and cache bottlenecks. The recovery plans provide guidance for solving performance problems. The recovery plan generation is supported for VSP 5000 series, VSP E series, VSP F series, VSP G series, VSP N series, VSP, and HUS VM series storage systems.

  1. From the E2E View, select a resource you want to analyze and click Analyze Bottleneck.

  2. In the Analyze Bottleneck window, click the Check Recovery Plans tab.

  3. Select one of the following options to generate a recovery plan:

    • Auto-Fill by Selecting an Event:
      • Click Browse Events to select an event. The metric that exceeded the threshold value and the event date and time are auto-filled when you select a bottleneck event.
      • Specify the target value for the metric.
    • Specify Manually:

      You must specify the following options manually:

      • Select the metric that exceeded the threshold.
      • Specify the date and time of the occurrence.
      • Specify the target value for the metric.
    NoteOps Center Analyzer supports generating recovery plans only for the following components and associated key performance metrics:
    • Processor: Utilization (MPB)
    • Cache: Write Pending Rate (CLPR)
  4. (Optional) Select Generate recovery plans for other resources used by the same consumer to generate recovery plans for the bottleneck resource, and other resources used by the same consumer.

  5. Click Generate Recovery Plans.

    View the system-generated recovery plans for the selected resource. A screenshot of the Check Recovery plans window.
  6. Review the recovery plans and apply an appropriate plan to solve performance problems.

Solving performance problems

 

The common performance problems and the possible solutions are described as follows. The possible causes and solutions are intended to provide guidance, and might not satisfy your business process performance requirements.

The following table lists the commonly observed storage-related problems and possible solutions.

Bottleneck metrics Root cause and possible solutions
Parity Group utilization
  • Root cause:

    The usage rate of the Parity Group increases because of the following possible causes:

    • Some volumes might be under heavy load.
    • Volumes (logical resources) might belong to the same Parity Group (physical resource) which might cause resource contention issues in the shared infrastructure.
  • Possible solutions:
    • Consider moving some volumes to another Parity Group with a lower usage rate or higher performance.
    • Consider increasing the number of drives (by concatenating Parity Groups).
    • To manage a Parity Group that is part of a pool, consider adding another Parity Group to the pool.
MPB utilization
  • Root cause:

    The usage rate of the MP Blade (average usage rate of the MP cores in the MP Blade) increases because of an increased load. Too many busy resources such as internal volumes, external volumes, or journal groups accessing the same MP Blade might cause performance degradation.

  • Possible solutions:
    • Consider allocating the busy resources (internal volumes, external volumes, or journal groups) to another MP Blade (changing the MP Blade ownership).

    • Limit I/O to the volumes using I/O controls.

    • Increase the size of cache memory allocated to the MP Blade.

Port utilization
  • Root cause:

    The usage rate of the port (amount of data forwarded by the port divided by the amount of data that can be forwarded by the port) increases because of a number of volumes accessing the same port.

  • Possible solutions:

    Consider allocating some volumes (or host groups) to a different port.

    Note: When the connected port is changed, the host might need to be restarted.

Cache utilization
  • Root cause:

    Out of the total cache memory allocated to the CLPR, the percentage occupied by the data waiting to be written to the drive increases. The cache write pending rate increases because of the following possible causes:

    • The usage rate of the drive might be high, delaying write processing to the drive.

    • The usage rate of the processors might be high, delaying write processing to the drive.

    • The capacity of the installed cache memory might be insufficient.

  • Possible solutions:
    • Consider allocating some volumes to another cache partition.

    • Consider increasing the cache memory.

    • Limit I/O to the volumes using I/O controls.

    • Consider allocating the busy resources (internal volumes, external volumes, or journal groups) to another MP Blade (changing the MP Blade ownership).

The following table lists the commonly observed server-related problems and possible solutions.

Bottleneck metrics Root cause and possible solutions
CPU utilization
  • Root cause:

    CPU bottlenecks occur when several VMs run on the same physical machine, and end up sharing the same CPU. If the VMs (logical resources) share the same CPU (physical resource) and if one of the VMs utilizes the CPU more than the others in the shared infrastructure, the total efficiency of the CPU is degraded and the CPU utilization rate increases. The CPU could become saturated with requests because of resource contention issues.

  • Possible solutions:

    Consider moving the VMs to another server.

Memory utilization
  • Root cause:

    Memory bottlenecks occur when several VMs (logical resources) share the available memory (physical resources) which might result in the performance degradation of the physical memory.

  • Possible solutions:

    Consider allocating additional physical memory, or moving the VMs to another server.

Executing actions

 

Execute predefined actions on a resource node. These predefined actions allow you to notify the appropriate IT administrators to troubleshoot the resource node problems.

Access the Execute Action window at any point during analysis from the following windows:

 

  • E2E View
  • Sparkline View
  • Analyze Shared Resources
  • Predictive analytics risk reports
  • Check Recovery Plans
  • Tools

Configure the system to perform the following actions:

  • Send email notifications

    For example, if a problem arises on a resource node, configure the system to send email notifications to the concerned administrator to troubleshoot the problem. Include the resource node information, troubleshooting methodology, and other information in the email template.

  • Run a command

    For example, if a problem arises on a resource node, execute the command action to automatically register the problem in a trouble-ticketing system, so that the concerned IT administrator can troubleshoot the node.

  • Submit a service through Ops Center Automator.

    For example, submit a service based on a template from Ops Center Automator to resolve a recurring problem.

  • Start granular data collection.

    For example, if your analysis requires data collection in intervals less than a minute, run the command for granular data collection.

Procedure

  1. From one of the entry points, click a resource icon, and then select Execute Action.

  2. In the Execute Action window, view the list of defined actions.

    The Actions list will be empty if you have not defined any actions previously. Following is the high-level procedure for creating event actions:
    1. Create an event action definition file and save it to the Ops Center Analyzer installation folder.

      Ops-Center-Analyzer-installation-folder/Analytics/conf

      The default installation folder is /opt/hitachi.

    2. Restart Ops Center Analyzer, or run the reloadtemplate command to view the defined actions.

  3. Under Actions, select an action.

    • To send email notifications, select the action type Mail and then click Launch Editor.

      The email template is launched in the email editor. Alter the email template to suit your requirements.

    • To run a command, select the action type Command.

      The details of the command are displayed. Edit the Command Arguments field, then click Execute Command. If you want to run more than one command at the same time, you can create a batch or shell command. In the Execute Command window, review the details of the command and then click OK.

    • To collect data at shorter time intervals, select Granular Data Collection or Granular Data Collection with Volume.

Hitachi Ops Center Automator integration

 

Ops Center Analyzer supports integration with Ops Center Automator.

This support allows users to directly access the service templates in Ops Center Automator from the Execute Action window in the Ops Center Analyzer UI. When you notice a performance problem in your shared infrastructure, you can run the appropriate action or service template to resolve it.

Submitting services through Ops Center Automator

 

Submit a service in Ops Center Analyzer based on built-in action templates or Ops Center Automator service templates.

In addition to running actions (such as email and CLI commands) through the Execute Action feature, you can submit services through Ops Center Automator when it is linked to Ops Center Analyzer. Some action templates already exist in Ops Center Analyzer. You can also access service templates available in Ops Center Automator.

Before you begin

  • Ops Center Automator must be linked to Ops Center Analyzer through the Common Component.
  • User permissions must be set for both Ops Center Analyzer and Ops Center Automator user accounts.
  • The definitions in the Ops Center Analyzer action templates must match those in the corresponding Ops Center Automator service names and service group names.

Procedure

  1. Click on the target resource and select Execute Action.

  2. In the Execute Action window, select the action or service template you want to submit, then do the following:

    • Scroll through the list of default action templates.
    • Check the box to see available service templates in Ops Center Analyzer
  3. Click Launch service execution, review the parameters in the Settings field, then click Submit:

    • If you are running a preexisting action, the parameters are autopopulated.
    • If you are running a service, you might need to enter the parameters manually.
  4. To monitor the task, click Launch Ops Center Automator from the Execute Action window.