Policy details

When you click a policy of interest in the table on the Policy UI, a side panel containing multiple information sections opens on the right-hand side of the table. Use the up and down arrows to navigate through the list of policies. Where permissions allow, you can Edit and Delete or enable and disable some policies here. You can also archive alert seasonality and temporal grouping policies that are not in use, or further investigate the justification for their creation directly from the side panel.

The four tabs that are displayed in the side panel are Details, Journal, Specification, and Source.

• Details:

  This tab displays the complete set of column data for the selected policy, including familiar fields, such as State, Status, Tags, Created by, Last modified by, Last run, and Execution status. The Last failure is the timestamp that the selected policy last failed. Number of failures indicates how many times the policy has failed, and Last failure details is the error message. Click Copy to copy Last failure details to the clipboard.

  The Matched number is incremented by 1 if one or more actions is proposed or performed by a policy. However, when errors occur during policy execution, matched might not be incremented. Therefore, you might see failures but the Matched count indicates 0. Matched may only be incremented upon successful policy execution.

  Note: In a case where an alert meets the incident-creation conditions of multiple policies, only one incident is created. However, all policies that proposed an incident, and the system incident creation policy will have the same Last run times. Each of these policies will also have their Matched counts incremented by one.

• Journal:

  The Journal tab displays any comments added by operators to record manual changes or updates to the policy. Comments are shown in chronological order. The policy creation date is also displayed.

• Specification:

  Shows you the key information about your conditions and policy. Each condition set of a policy is detailed in the Specification tab, as well as what is created by the policy.

• Source:

  View a policy in its raw form in either JSON or YAML format, depending on your requirements. Click Copy to copy the policy data to the clipboard.

Note: Preset policy names and internal action references to "story" or "stories" are synonymous with incidents. Incident triggers and condition references supported in the "Invoke IBM Tivoli Netcool/Impact" policy template are stored as story. For policy search based on conditions, use "story" instead of "incident". For example, to find incident.title in a policy search, use story.title. These internal references and policy names have no bearing on actual behavior and are for internal processing purposes only. Any references to "story" in preset policy names, or other policy details or specifications is not an error, and is equivalent to incident in all respects.