Overview

Skill Level: Any Skill Level

This recipe explains about the following.

1. Incident details - Notification messages are not received
2. Configuring Threshold
3. Configuring Runbook
4. Configuring Event Policies
5. Configuring Incident Policies

Ingredients

IBM Cloud Pak for Multicloud Management 1.3.0 (MCM Hub)
Redhat Openshift Container Plantform 4.3 (Managed Clusters)

Step-by-step

  1. Introduction

    MCM leverages the following objects for Application Monitoring and Incident management.

    Thresholds
    Runbooks
    Event Policies
    Incident Policies

    This document explains about how to create and configure those objects for an use case Notification messages are not received.

    Here is the use case and incident handling flow.

    027-notification-flow-2

  2. Incident - Notification Alerts

    We are going to create and configure the following.

    • Threshold for MQ Queue Not being Read
    • Threshold for Notification Saturation High
    • Runbook for Notification Runbook
    • Event Policies for MQ Queue Not being Read
    • Event Policies for Notification Saturation High
    • Incident Policies for Notification Alert

    Here is the sample incident with events and runbook.

    Incident Summary

    022-incident-notfication-inbox

    Incident Details – Notification Saturation High

    023-incident-notfication-event-saturation-1

    Incident Details – MQ Queue Not being Read

    024-incident-notfication-event-mq

    Incident Details – Runbook associated

    025-incident-notfication-runbook

  3. Goto Administration Page in MCM Console

    Click on the Infrastructure Monitoring

    001-menu-1

  4. Configuring Threshold

    Goto Threshold Page

    Click on the Threshold card

    002-card-threshold-1

    Create Threshold for MQ Queue Not being Read

    Here is the list of threshold created. You can click on Create button to create a new one.

    003-threshold-home-1

    Here is the threshold configuration for MQ Queue Not being Read.

    Enter the parameters as highlighted.

    Current Depth > 0
    Input Opens < 1

    Output Opens > 0

    004-threshold-mq-1

    004-threshold-mq-2

    004-threshold-mq-3

    004-threshold-mq-4

     

    Create Threshold for Notification Saturation High

    Here is the threshold configuration for Notification Saturation High.

    Enter the parameters as highlighted.

    – Saturation > 60 percent
    – Service Name contains wealthcare-web

    005-threshold-saturation-1

    005-threshold-saturation-2

    005-threshold-saturation-3

     

  5. Configuring Runbook

    Goto Runbook Page

    Click on the Runbook card

    008-card-runbook-1

    Create Runbook for Notification Runbook

    Here is the list of Runbook created. You can click on Create button to create a new one.

    008-runbook-notification-1

    Here is the Runbook configuration for Notification Runbook.

    Enter the parameters as highlighted.

     

    008-runbook-notification-2

  6. Configuring Event Policies

    Goto Event Policies Page

    Click on the Policies card

    030-card-policies-1

    Create Event Policies for MQ Queue Not being Read

    Here is the list of event policies created. You can click on Create button to create a new one.

    010-event-home-1

    Here is the Event Policy configuration for MQ Queue Not being Read.

    Enter the parameters as highlighted.

    Here the event type attribute value refers to the threshold that we created in the previous steps.

    012-event-mq-1

    012-event-mq-2

    012-event-mq-3

    Enrich

    Here we enrich the event with Application = Wealthcare Notification Alert.

    This event enrichment will ensure all the events with the Application = Wealthcare Notification Alert are correlated into one incident with the name Wealthcare Notification Alert

     

    Create Event Policies for Notification Saturation High

    Here is the Event Policy configuration for Notification Saturation High.

    Enter the parameters as highlighted.

    Here the summary attribute value refers to the threshold that we created in the previous steps.

    013-event-saturation-1

    013-event-saturation-2

    013-event-saturation-3

    Enrich
    Here we enrich the event with Application = Wealthcare Notification Alert.

    This event enrichment will ensure all the events with the Application = Wealthcare Notification Alert are correlated into one incident with the name Wealthcare Notification Alert

     
    Runbook
    Here assign the previously created runbook Notification Runbook

  7. Configuring Incident Policies

    Goto Incident Policies Page

    Click on the Policies card

    030-card-policies-1

    Create Incident Policies for Notification Alerts

    Here is the list of Incident policies created. You can click on Create button to create a new one.

    014-incident-home-2

    Here is the Incident Policy configuration for Notification Alerts.

    Enter the parameters as highlighted.

    Here the Application attribute value refers to the Wealthcare Notification Alert enrichment that was done in the previous step.

    015-incident-notification-1

    015-incident-notification-2

    015-incident-notification-3

    Group

    Assinged the incident to wealthcare group.

    Priority
    Set the priority 1 for this incident.

     

Join The Discussion