Preetdeep Kumar

Monitoring CA Mediation Manager (Part 2)

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

This is a continuation of a previous post on the same subject.

 

Overview

In this post, I will talk about "CAMM_IM_SelfMonitoring", a self-monitoring device pack available in CAMM. This one device pack can monitor all the Engines installed on a Local Controller (LC). It consumes very less system resource and has fast processing time.

 

Metrics

The metrics collected by CAMM_IM_SelfMonitoring device pack are grouped under two metric families:

  1. CAMM_IM_SelfMonitoring ENGINE: Metrics collected from each Engine such as:
    • CPU and Memory Usage
    • Number of devices polled, Number of metrics polled
    • Time taken to complete a poll
    • Number of files failed to processed
  2. CAMM_IM_SelfMonitoring ALLENGINES: Average of selected metrics collected from each Engine such as:
    • Average CPU and Memory usage
    • Peak CPU Usage

 

As of current version of CA Mediation Manager 3.1, there are total of 26 metrics collected for each Engine and 8 metrics collected for ALLENGINE.

 

Dashboard

This device pack comes with out of the box dashboards. In CA Performance Center, under Inventory tab you can click on either of "Device" and "Device Components" and then click on the Engine name.

The naming convention in Device is <LocalController-Hostname>_<DevicePackName>

The naming convention in Device Component is ENGINE-<DevicePackName> for individual Engines and ALLENGINES-<LocalControllerHostname> for all Engines

 

Notification

To have a better monitoring experience from this device pack, I recommend to create Threshold profiles which will allow CA Performance Center to create event and send notification. 

E.g. You can choose to get notification if Number of Files processed is Equal To Or Below 0 which indicates either Engine is down or it was not able to get data from EMS.

Outcomes