threshold_migrator Supported Probe Considerations

The threshold_migrator probe is configured to enable standard static thresholds in probes across all hubs in a domain. Once a probe is migrated, a Static Alarms section is displayed with the probe-specific alarm configurations in the monitor threshold configuration page. The Infrastructure Manager GUI is no longer available.
uimpga-ga
The threshold_migrator probe is configured to enable standard static thresholds in probes across all hubs in a domain. Once a probe is migrated, a 
Static Alarms
 section is displayed with the probe-specific alarm configurations in the monitor threshold configuration page. The Infrastructure Manager GUI is no longer available.
 
Contents
 
 
 
Supported Probes
The probe migrates the threshold configuration for the following probes:
 For information about version-specific support for the probes, see threshold_migrator (Threshold Migrator) Release Notes.
  • ad_server (Active Directory Server Monitoring) 1.80 or later
  • dirscan (File and Directory Scan) version 3.12 or later
  • exchange_monitor ((Microsoft Exchange Monitoring) version 5.20 or later
  • iis (IIS Server Monitoring) 1.71 or later
  • logmon (Log Monitoring) version 3.49 or later
  • lync_monitor (Microsoft Lync Server Monitoring) 2.20 or later
  • net_connect (Network Connectivity Monitoring) 3.11 or later
  • ntperf (Performance Collector) 1.90 or later
  • rsp (Remote System Probe) 5.10 or later
  • sharepoint (Microsoft SharePoint Server Monitoring) 1.70 or later
  • url_response (URL Endpoint Response Monitoring) 4.20 or later
 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 the 
Known Issues
 section in the 
ppm
 probe documentation for the migrated probes to view the limitations of using Admin Console.
Supported Probe Prerequisites
  • baseline_engine, ppm, and threshold_migrator must be on the remote hub for the threshold_migrator to update the probes correctly.
  • Migration of the following probes using the threshold_migrator probe have the following prerequisites, as applicable:
    •  
      url_response
      : The 
      useHostNameForDeviceIdentification
       key in the 
      Setup
       section of 
      Raw Configuration
       of the url_response probe must be set to 
      yes
      .
    •  
      iis
      : The 
      useRobotDevIDForLocalhost
       key in the 
      Setup
       section of 
      Raw Configuration
       of the iis probe must be set to 
      yes
       to monitor the health and status of local Microsoft IIS servers.
Probe-Specific Changes After Migration
This section lists the probe-specific changes for supported probes after migration. The common changes to all the probes are listed in the threshold_migrator (Threshold Migrator) Release Notes.
dirscan (File and Directory Scan)
The 3.13 or later version of the probe has the following changes after migration:
  • The units in all profiles in the migrated probes revert to the default values and must be reconfigured, if needed.
  • Operators reverse in their logic (Refer 
    Operator Reversal after Migration
     in probe document).
  •  
    QOS_DIR_AGE
    : Alarm is generated for the 
    newest file
     after migration if configuration is set to 
    individual file
     before migration.
  •  
    QOS_DIR_RESPONSE_TIME
    : Alarm is generated for the 
    longest file
     after migration if configuration is set to 
    individual file
     before migration.
The 3.12 version of the probe has the following additional change after migration:
  • Dynamic values such as $File are not available. The values are available if a migrated probe is upgraded to version 3.13 or later. The values are also available if the probe version 3.13 or later is migrated using threshold_migrator version 2.10 or later. 
exchange_monitor ((Microsoft Exchange Monitoring)
The 5.20 or later version of the probe has the following changes after migration:
  • The static message variables are migrated and only the standard variables such as value and threshold will be used.
  • The variable syntax changes from 
    $<variableName>
     to 
    ${<variableName>}
    .
  • DAG Monitors with Sate or Boolean units will not be migrated. The probe will continue to send these alarms.
  • The dynamic variable ${value} changes to ${last_value} in alarm messages for Perfmon probe.
  • After migration, the QoS sent by the probe will contain the average values and not the current value, if sampling is selected.
  • Operators reverse in their logic (For more information about 
    Operator Reversal after Migration
    , see exchange_monitor (Microsoft Exchange Monitoring) Release Notes).
net_connect (Network Connectivity Monitoring)
The 3.11 or later version of the probe has the following changes after migration: 
  • The QOS_NET_CONNECT, that monitors the ping response, cannot be migrated.
ntperf (Performance Collector)
The 1.90 or later version of the probe has the following changes after migration:
rsp (Remote System Probe)
The 5.10 or later version of the probe has the following changes after migration:
  • The thresholds for only CPU, Disk, Memory, and Processes of the rsp probe are migrated.
  • The 
    Send Average Value in QoS
     and 
    Send Qos per Process Instance
     fields on the 
    rsp
     node get enabled, if disabled. These two fields must be enabled for Standard Static Thresholds to work.
  • The QOS_PROCESS_STATE, that monitors the state of the process, cannot be migrated.
  • The alarms for WMI objects continue to be generated even though these are not configurable from the Admin Console.
  • The higher threshold is migrated for any monitor having same severity for both high and low threshold.
  • Probe template configurations from the IM GUI are migrated and displayed on the Admin Console GUI.
  • The 
    Publish Alarms
     checkbox is applicable only for the static alarms.
  • QoS and alarms are not generated for monitors that are selected from the Admin Console but are not part of a group.
url_response (URL Endpoint Response Monitoring)
The 4.21 or later version of the probe has the following change after migration:
  • The url_response probe displays all its alarms individually instead of displaying only one alarm with the highest priority. If not migrated, the probe only generates one alarm that is based on the alarm priority.
    For more information, refer the 
    url_response
     probe documentation.
The 4.20 version of the probe has the following additonal change after migration:
  • Dynamic values in alarms are not available. The values are available if a migrated probe is upgraded to version 4.21 or later. The values are also available if the probe version 4.21 or later is migrated using threshold_migrator version 2.01 or later.