Preetdeep Kumar

Monitoring CA Mediation Manager (Part 1)

Blog Post created by Preetdeep Kumar Employee on Mar 21, 2017

   Overview

This is going to be series of posts focusing on various ways to monitor CA Mediation Manager (CAMM).

You will need to monitor CAMM if you are interested in:

  • Receiving a notification when an anomaly occurs
  • Understanding how much system resources (CPU, Memory, Java threads) are being consumed by device packs

In this post, I will talk about the Anomaly Detection (AD) feature of CAMM and ways to customize it based on your preferences.

 

Details

CAMM comes with a built-in anomaly detection feature which allows you to select anomalies and provide a list of email addresses to send notifications to when an anomaly is detected. This feature can be enabled in the CAMM Web UI under “My Settings” tab. Find out more here.

Before you enable this feature, it is recommended to test the email settings by clicking on the “Test” button. CAMM will send a test email to all the participants in the To and CC fields with a default dummy address of CAMM-Notification@ca.com.

Skip this “Test” step if your email server doesn’t allow for anonymous emails

Provide valid email address in From field if your email server doesn't allow for dummy address

Once you have saved your settings, CAMM will start monitoring its components (MC, LC, Engine and Presenter) for anomalies. Underlying this feature is a rule-based approach where each rule is used to assert a condition and execute an associated action.

The rules and actions are saved in a XML file under $CAMM/AD/AnomalyConfigBase/<component_name> folder structure.

For Local Controller files are saved on a Linux system under /opt/CA/CAMM/AD/AnomalyConfigBase/LC_ANOMALY/*

 

How to customize

You can customize this feature by editing the rules and anomalies file as follows:

 

Rules

Rules are saved in a file named <component_ID>_Rules.xml under their respective component folder.

/opt/CA/CAMM/AD/AnomalyConfigBase/LC_ANOMALY/LC-10.11.12.13_Rules.xml stores all rules defined for Local Controller installed on 10.11.12.13 

  1. Frequency - This value is used by CAMM to periodically evaluate conditions for asserting this rule. Measured in seconds, you can edit this to any positive integer.
  2. Name - This value is displayed in the Web UI if you select this component. You can edit this to any string of your choice.
  3. Multiple conditions - You can add multiple <if> blocks to add more conditions for a rule. Actions will be executed only when all the conditions are evaluated.

Each rule has an <anomaly> element which acts as a key and is used to select an action to perform

Action

Actions are defined in a file named Anomalies.xml under their respective component folder.

  1. Value of <subject> and <title> elements are used as Email subject and title when this anomaly occurs. You can edit these values to your choice.
  2. You can add more troubleshooting tips or remove some based on your environment by editing value of <troubleshooting> element.
  3. You can add more context to the email by using variables. When an anomaly occurs, CAMM will replace these variables by actual value before sending email. See attachment for complete list of supported variables per component.

    $getCompID is one such variable used in Engine's Anomalies.xml file which gets replaced by the Engine name

 

      

What's next

In my next post – I’ll talk about a device pack named CAMM_IM_SelfMonitoring. With this device pack, you can visualize performance stats of your device packs in CA Performance Management (CAPM). You can also set events based on the metrics collected by this self-monitoring device pack and get notifications from CAPM.

Outcomes