threshold_migrator (Threshold Migrator) Release Notes

 
uimpga-ga
threshold_migrator_RN
The threshold_migrator probe allows you to migrate the probe threshold configuration values to the standard static threshold configuration of the baseline_engine. Migration also includes custom alarm messages. The advantages of standard static threshold configuration are:
  • Consistent threshold configuration options (for all probes that support it)
  • Ability to configure “Time Over Threshold” for static thresholds
  • Support for five different threshold levels (most probes support one or two levels)
Migration is supported for the specified version or later of the probes using CA UIM 8.31 or later for threshold_migrator.
 
 
Contents
 
 
 
Revision History
This section describes the history of the revisions for the threshold_migrator probe.
 
Version
 
 
Description
 
 
State
 
 
Date
 
2.11
 
What's New:
 
  • Added support to migrate the exchange_monitor probe to standard static thresholds.
GA
September 2015
2.10
 
What's New:
 
  • Added support to migrate the net_connect probe to standard static thresholds.
  • Added support to migrate dynamic alarm variables in dirscan 3.13 or later.
GA
August 2015
2.01
 
What's New:
 
  • Added support to migrate the following probes to standard static thresholds:
    • ad_server
    • iis
    • lync_monitor
    • rsp
    • sharepoint
  • Added support to migrate probes on all hubs in a domain.
  • Added support to view robot specific migration error details.
 
June 2015
1.10
 
What's New:
 
  • Added support to migrate the url_response probe to standard static thresholds.
  • Added support for robot specific migration.
 
May 2015
1.00
First release of the probe.
 
March 2015
Supported Probes
The 1.00 and later versions of the probe migrate the threshold configuration for the following probes:
  • dirscan (File and Directory Scan) version 3.12 or later
  • logmon (Log Monitoring) version 3.49 or later
  • ntperf (Performance Collector) 1.90 or later
The 1.10 and later versions of the probe also migrate the threshold configuration for the following probes:
  • url_response (URL Endpoint Response Monitoring) 4.20 or later
The 2.01 and later versions of the probe also migrate the threshold configuration for the following probes:
  • ad_server (Active Directory Server Monitoring) 1.80 or later
  • iis (IIS Server Monitoring) 1.71 or later
  • lync_monitor (Microsoft Lync Server Monitoring) 2.20 or later
  • rsp (Remote System Probe) 5.10 or later
  • sharepoint (Microsoft SharePoint Server Monitoring) 1.70 or later
The 2.10 and later versions of the probe also migrate the threshold configuration for the following probe:
  • net_connect (Network Connectivity Monitoring) 3.11 or later
The 2.11 and later versions of the probe also migrate the threshold configuration for the following probe:
  • exchange_monitor ((Microsoft Exchange Monitoring) version 5.20 or later
Changes After Migration
After migration, the 
baseline_engine
 probe sends the alarms for these probes. The alarm thresholds can only be configured from the Admin Console. Refer Configuring Alarm Thresholds for information about how to configure the static thresholds after migration. Also, the Admin Console GUI of the probe displays the static alarms and time over threshold configurations. You cannot configure the probe-specific alarm configurations to generate alarms.
After migration, the following elements of the migrated probe are not available:
  •  
    Infrastructure Manager GUI
    Opening the IM GUI displays a message that the probe can only be configured using the Admin Console. You are then redirected to the Release Notes for the probe.
  •  
    Automated rollback
    The probe does not support rollback. A backup of the config file for each instance of the probe is created in the threshold _migrator installation directory for reference.
Some changes to alarms after migration are as follows:
  • Alarm messages that are sent by the baseline_engine do not yet support internationalization. The alarm messages are not automatically translated or displayed in non english languages. However it is possible to use non english characters to customize alarm messages.
  • The 
    $
     variables that are used in probe alarm messages are migrated.
    The variable syntax changes from 
    $<variableName>
     to 
    ${<variableName>}
    .
  • Static message variables are also migrated and replaced with standard variables such as 
    $value
     and 
    $threshold
    .
  • When you create new profiles for monitoring, customize the alarm messages in the profile, as needed. If no alarm message is configured, baseline_engine uses a default alarm message string. The default string can be different from the probe alarm messages in other profiles.
For more information about probe-specific changes, see the 
threshold_migrator Supported Probe Considerations
 article .
 The IM GUI of a migrated probe is not available after the probe is migrated using threshold_migrator. The migrated probe can only be configured using the Admin Console GUI.
Refer 
Known Issues
 in the 
ppm
 probe documentation for the migrated probes to view the limitations of using Admin Console.
Probe Specific Hardware Requirements
The threshold_migrator probe must be installed on systems with the following minimum resources:
  • Memory: 2-4 GB of RAM. The OOB configuration of the probe requires 256 MB of RAM
  • CPU: 3-GHz dual-core processor 32, or 64 bit
Probe Specific Software Requirements
The threshold_migrator and its supported probes have the following software requirements:
  • CA Unified Infrastructure Management 8.31 or later
  • Robot 7.62 or later (recommended)
     Robot 7.70 is required to migrate the 
    url_response 
    probe.
  • Java JRE version 7 or later
  • PPM (Probe Provisioning Manager) probe version 3.22 or later
  • baseline_engine (Baseline Engine) version 2.60 or later