10 Problems Knowledge Base

The Problems Knowledge Base contains annotations based on asset type. Annotations are text files or shell scripts that can automate an operation, provide a suggested action, or record a comment. An administrator can associate an annotation with a problem and an asset type that can help a user to investigate or fix a Problem when it occurs for a specific asset type.

This section provides an overview of the Problems Knowledge Base and how to add annotations to the Problems Knowledge Base and how to remove them.

About the Problems Knowledge Base

Annotations in the Problems Knowledge Base are created, updated, and deleted by a user with Enterprise Controller Admin or Admin permissions. Annotations are defined by an asset type, asset resource type, an attribute, or a problem type.

The following types of Annotations are available:

  • Automated Operation – Enables you to create an annotation that references an Operational Profile and automatically executes the profile when a specific problem occurs.

  • Suggested Action – Enables you to provide a suggested fix or course of action for a specific problem. The suggested course of action can be text only, or you can reference an Operational Profile.

  • Comment – A text only field that you can use to write notes about the situation, such as the current status of a problem.

As an administrator, you can add annotations to the Problems Knowledge Base that provide solutions or recommended actions for specific problems. You can also add an annotation to the Problems KB when you add an annotation to a specific problem.

When a problem is detected, Ops Center checks the Problems Knowledge Base and Problem Profiles for the asset type and corresponding problem type. Any associated Annotations are added to the Problem and Operational Profiles referenced in Automated Operation annotations are executed against the asset on which this problem was open.

Adding an Annotation to the Problems KB

Annotations are created by a user with Ops Center administrator permissions and are defined by an asset type, asset resource type, an attribute, or a problem type. The annotations are stored in the Problems Knowledge Base (KB) and can be automated operations with associated operational profile, suggested fixes or actions, or text only comments. An administrator can associate Automated Action and Suggested Action annotations with an operational profile, which can contain a script.

You can also add an annotation to the Problems KB when you add an annotation to a specific problem, as described in "Adding an Annotation".

To Add an Annotation to the Problems KB

  1. Click Plan Management in the Navigation pane, expand Operational Plans, then expand Problems Knowledge Base.

  2. Select the asset type. The Annotations associated with the asset type are displayed in the center pane.

    1. Click the Add icon in the center pane. The Add Problem Type Annotation page appears.

  3. Define the Problem Type. The attributes displayed depend upon the target and Asset Type.

    1. Select an Asset Type from the drop-down menu.

    2. Select a Monitored Attribute from the drop-down menu or enter an attribute to be monitored. For a list of valid attributes for each asset type, see the javadoc public API.

      Note:

      The drop-down menu for asset type and monitored attribute are retrieved from the Monitoring Rules deployed on the setup. If an attribute is not listed, it is not monitored. To add an attribute to the menu, define a Monitoring Rule for this attribute as described in Adding a Monitoring Rule. To enter an attribute that is not in the drop-down menu, you can use a wildcard such as CpuUsage.*.
    3. Define the list of severities to which this annotation applies. The annotation is added to a Problem only once, at creation or the first time this Problem reaches one of the severity levels defined here. When the annotation is an Automated Action, the associated operational profile is executed as soon as it is added to the Problem.

  4. Determine the Annotation to associate with the problem.

    1. Select the Annotation Type from the drop-down menu. The following options are available:

      • Comment – Text only option that is designed to be used to add a note or editorial comment.

      • Suggested Action – Text is required. An Operational Profile is optional.

      • Automated Action – Text and an Operational Profile are required.

  5. Select an operational plan from the drop-down menu. The operational plans presented in the drop-down menu are your organization's custom scripts and operational profiles. Automated actions must have an associated operational plan.

  6. The Synopsis field is automatically completed based on the asset type. Edit the synopsis, as needed.

  7. Type a description or instructions in the Note field.

  8. Click Save.

Removing an Annotation From the Problems KB

Annotations in the Problems Knowledge Base (KB) are associated with types of problems. A user with an Ops Center administrator role can delete an annotation in the the Plan Management section of the user interface.

To Remove an Annotation From the Problems KB

  1. Click Plan Management in the Navigation pane, then expand Operational Profiles.

  2. Expand Problems Knowledge Base in the Navigation pane, then select the target type. The annotations associated with the target type are displayed in the center pane.

  3. Highlight the annotation you want to delete, then click the Delete icon. The Delete Problem Type Annotation page appears.

  4. Click Delete.