mon_config_service Key Value Reference
This article describes the mon_config_service probe settings that are visible in Raw Configure. The default settings should be applicable for most environments. Modify the advanced configuration settings only when advised by support.
This article describes the mon_config_service probe settings that are visible in Raw Configure. The default settings should be applicable for most environments. Modify the advanced configuration settings only when advised by
(mon_config_service v8.44 and earlier) Profile Reconciliation Options
Navigation:mon_config_service > profilereconcile
After configuration profiles are applied to probes on target devices, the mon_config_service probe reconciles any
manualconfiguration changes at regular intervals. This process is named reconciliation. (Manual configuration changes are any changes made manually to a probe, or changes made using Admin Console or Infrastructure Manager.)
During reconciliation, the mon_config_service probe interrogates target devices with probe configurations that are managed by Monitoring Configuration Service. When the probe interrogates the target devices, it requests their configurations. When there are differences between the expected configuration and the existing configuration, mon_config_service performs the configured profile reconciliation action. See the action description.
For group and device profiles, you can select the reconciliation action. The reconciliation action is defined using
Raw Configureto access the mon_config_service probe properties. The following keys dictate how the mon_config_service probe performs profile reconciliation.
- action:The action that is taken during profile reconciliation when a difference is found between the profile configuration and the probe configuration. Valid values include:
- Audit - Add the configured profile value found to be in conflict with the probe configuration value to the audit log.
- Alarm - Emit an alarm indicating which profile configuration value was in conflict with the probe configuration.
- Redeploy - Reinstall the probe and redeploy the profile configuration.
- Overwrite - Mark the monitoring profile as modified to force the profile to be redeployed to the probe.
- active: Enables profile reconciliation.Default: Yes
The profile reconciliation functionality is now available with the MCS Utilities Tools.
Advanced Configuration Settings
The settings that are described in this section are mainly for reference purposes. If you contact CA Support for help to diagnose a technical issue, you can refer to this section if a support representative asks you to modify one of the key values.
Do not attempt to change any of the key values that are included in this section unless you are working with
CA Support, a Presales representative, a Professional Services representative, or you have a thorough understanding of how to use the Monitoring Configuration Service to configure and manage profiles.
(mon_config_service v9.0) Migration Settings
Navigation:mon_config_service > migration
The configuration key available in this section pertains to the migration of the existing profile instances:
- enable_auto_migration:This key helps you automatically migrate existing profile instances to the latest version of the installed probe templates. You control whether or not the new probes template package automatically migrates existing profile instances to the latest version of the installed probe templates. To configure MCS to migrate all existing profiles, you use the new /migration/enable_auto_migration MCS configuration key. The default value for the /migration/enable_auto_migration key is false. If you keep the default value of false, the probe templates package imports the probe templates from the probe templates package installation file, but does not migrate any of the existing profiles.Default: False
(mon_config_service v8.6) Audit Settings
Navigation:mon_config_service > audit
The configuration keys available in this section pertain to the clean up (the "garbage collection") of the audit trail history.
- garbage_cleanup_interval_minutes: The frequency at which the garbage collection process is executed.Default: 20
- garbage_cleanup_batch_size: The number of records that are removed during each garbage collection interval.Default: 10000
- days_in_audit_trail_history: The number of days of audit trail history that are kept in the SSRV2Audittrail and SSRV2AudittrailModification tables. If you use the default setting of 30 days, then any audit trail history that is older than 30 days is cleaned up. To help with debugging, the last configuration that you made that is older than 30 days old, is not cleaned up.Default: 30Note: Do not set the days_in_audit_trail_history to less than 1.If you have a large number of records in the SSRV2Audttrail and SSRV2AudittrailModification tables that you want to clean up, decrease the cleanup interval minutes and decrease the batch size rather than increase the batch size. We recommend a batch size of less than 50000.
Connection Pool Setting
Navigation:mon_config_service > connection_pool
The configuration keys available in this section pertain to the database connection pool.
- default_query_timeout_seconds: The database query timeout.Default: 30 seconds
- initial_pool_size:The number of database connections to open on startup.Default: 10
- max_pool_size:The maximum number of database connections to allow.Default: 200
- validation_query_timeout_seconds: The timeout (in seconds) to use for validating the database connection.Default: Five
(mon_config_service v8.50) Deploy Setting
Navigation:mon_config_service > deploy
The configuration keys available in this section pertain to the deployment queue.
- queueSize: The number of profile deployment tasks in the deployment queueDefault: 1000 tasks
Navigation:mon_config_service > discovery
The configuration keys available in this section pertain to dynamic data requests and retrieval.
- auto_install_probes:When it is discovered that a probe is not installed during profile deployment, this parameter determines whether a probe is automatically installed.Default: no
- discoveryidlewait:The amount of time (in seconds) to wait before checking for new requests for dynamic data.Default: 30 seconds
- discoverythreads:The number of threads to use to request dynamic data from the target devices after a probe is installed and configured. The dynamic data is retrieved using callback requests.Default: 10
- evalrefreshintervalminutes:The amount of time (in minutes) between waiting before creating a new dynamic data request and re-evaluating the device profiles. The purpose is to update existing system configuration that is based on changes in the environment that are being reported/discovered from the probe.Default: 60 minutes
Password Encoding Settings
Navigation:mon_config_service > password_encoding
This section provides the password encoding to used when encrypting password fields in a probe configuration file.
- dirscan: ISO-8859-1
- email_response: ISO-8859-1
- ews_response: ISO-8859-1
- exchange_monitor: ISO-8859-1
- iis: ISO-8859-1
- mysql: UTF-8
- oracle: ISO-8859-1
- processes: UTF-8
- sqlserver: UTF-8
- url_response: ISO-8859-1
(mon_config_service v8.44 and earlier) Profile Reconcile Settings
Navigation:mon_config_service > profilereconcile
The advanced reconciliation configuration keys available in this section relate to queuing and reconciling profile changes.
- active: When you set this value to yes, MCS performs reconciliation. When you set this value to no, MCS does not perform reconciliation.Default: Yes
- checkFrequencyMins: The amount of time to wait after a profile was successfully deployed before checking to determine if a profile configuration was changed using a method other than the USM Monitoring tab (such as accessing the probe GUI using Admin Console).Default: 1440 minutes (24 hours)
- interval:How often threads check for deployed profiles to be reconciled.Default: 300 seconds
- queueSize:The total number of profiles in the queue to be reconciled.Default: 1000
- threads:The number of threads to use for profile reconciliation.Default: 4
Navigation:mon_config_service > setup
The configuration keys available in this section pertain to the setup of the mon_config_service probe.
- automated_deployment_engine: Indicates whether automated_deployment_engine or distsrv manages the probe and package distribution.Default: automated_deployment_engine
- data_engine:If you deploy the mon_config_service to a robot, enter the location where the data_engine probe resides. Use the format: /<domain>/<hub>/<robot>/data_engineDefault: data_engine
- loglevel:Select the amount of log information you would like to collect for this probe.0 = Fatal1 = Error2 = Warning3 = Information4 = Debug5 = TraceDefault: 1 (Recommended)
- query_timeout_seconds:A database query timeout Default: 300 seconds
- utf8_supported_adapter_list:A list of probes and versions that support UTF-8 encoding.
- adevl_2 Default: 2.00
- ad_server Default: 1.70
- (mon_config_service 8.50) log_forwarder 1.00
- logmon Default: 3.40
- ntevl_4 Default: 4.00
- ntperf Default: 2.00
- ntperf64 Default: 2.00
- perfmon Default: 1.60
- rsp_4 Default: 5.00
- (mon_config_service 8.50) url_response 3.9
- nimpool_max_active:Maximum number of elements in NimPool - Default: 200
- nimpool_max_idle:Wait time for a free element in Nimpool - Default value: 20 seconds
- nimpool_timeout:How long a free element is alive before it is closed - Default value: 20 seconds
- nimpool_max_wait:Timeout waiting for an answer from "the other side" - Default value: 20 seconds
Navigation:mon_config_service > startup
The configuration keys available in this section are used from the process controls of the mon_config_service probe.
- options:Additional Java process configuration parameters Default: -Xms512 -Xmx1024m
Navigation:mon_config_service > statistics
The configuration keys available in this section determine whether the mon_config_service probe generates QoS messages.
- active:Enables the probe to calculate QoS metrics and generate of QoS messages.Default: yes
- interval:The frequency to compute QoS metrics and generate QoS messages.Default: 1 minute
See the mon_config_service Metrics article for details about the QoS data the mon_config_service probe generates.
Navigation:mon_config_service > templates
The configuration keys available in this section pertain to tasks performed by the mon_config_service probe to manage templates.
- directory:The directory, relative to the probe installation directory, where the mon_config_service probe looks for the template files.Default: templates
- interval:The time interval (in seconds) that the mon_config_service probe looks for new template files.Default: 60 seconds
Navigation:mon_config_service > timed
After the mon_config_service probe applies configuration profiles to probes on target devices, the probe monitors the UIM environment for changes at regular intervals. Changes in the following UIM components are monitored according to configured intervals:
- Group configuration or membership - If target devices are added or removed from a group, these changes are reconciled every 15 minutes.
- Group or device profiles - If configuration profiles are modified or a profile is deleted, this change is applied every 1 minute.
The configuration keys available in this section pertain to housekeeping and recurring tasks that are performed by the mon_config_service probe.
- charset_cache_expiration_hours:The amount of time Monitoring Configuration Service stores, in cache, the calculated character encoding (or charset) in use for each robot it configures. If character encoding changes on a robot, Monitoring Configuration Service recalculates character encoding when cache expires.Default: Six hours
- (mon_config_service v8.50) check_device_offline_minutes:How often the mon_config_service probe checks to see if it can deploy a probe configuration profile to a target device that was previouslyunreachable. When a robot on a target device has a status ofunreachable, any probe configurations that are destined for that device are postponed until the robot status changes took.Default 15 minutes
- (mon_config_service v8.50) config_deployment_threads:The number of threads mon_config_service uses to to deploy configuration profiles to CA UIM probes.Default: 100 threads
- device_id_fields:The names of the columns on the CM_COMPUTER_SYSTEM table to use when selecting unique devices from the CM_COMPUTER_SYSTEM table to publish for secondary discovery.Default: name, origin
- device_interval:The frequency to check for changes to devices. Detected changes to devices can be: a device is added or removed from a group, device configuration profiles are modified or deleted, or a probe is uninstalled from a device. For bulk deployments the values can range from 180-1200.Default: 120 seconds
- (mon_config_service v8.50) device_processing_threads:The number of threads mon_config_service uses to evaluate group configuration profiles and create the resulting device configuration profiles.Default: 30 threads
- force_profile_delete_on_error: Set this value to true if you want MCS to delete a configuration profile when a robot on a target device in unreachable. The configuration profile is removed from the system after MCS attempts the maximum number of retries.If a robot is unreachable while MCS attempts to delete a configuration profile for a target device, and the force_profile_delete_on_error value is set to true, MCS will delete the profile from the system after the maximum number of retries is reached. However, the configuration profile remains applied to the probe on the target device. This means that once the robot becomes active again, the configuration profile remains applied to the probe, and the probe begins to emit alarms and QoS metrics based on the applied configuration. To remove the configuration that is applied to the probe on the target device, you can remove the probe from the target device. Then copy a configuration profile to the USM group, or make a change to the group configuration profile where the target device is a member.Default: False
- group_interval:The frequency to check for changes to group membership for groups with a Group Profile assigned. Devices can be added or removed from a group. Also the frequency to add a device or remove a device from a group that was created using a SQL query or a Regular Expression.Default: 900 seconds
- max_device_cache_age_seconds:The maximum age (in seconds) before a device is removed from the discovery cache.Default: 900 seconds (15 minutes)
- max_device_cache_size:The maximum number of devices to cache from discovery.Default: 1000
- max_retries:The maximum number of times to attempt to deploy a profile that is in error.Default: 30
- maxdaysinactivedeviceprofiles:The maximum number of days that a probe can be inactive before its profile is deleted. An inactive profile has status=error for the number of days that are configured for this key.Default: 7
- resolve_ip_using_device_id_fields:If a device address is not present, use the populated profile fields to resolve the device network address.Default: trueTheresolve_ip_using_device_id_fieldskey value is available after you install CA UIM Service Pack 1 (SP1) and are running mon_config_service 8.42 on your Primary Hub.
- check_package_availability:Package availability check for a template is performed based on this parameter. Default: true
- check_package_availability_interval:The frequency of the package availability check is performed is based on this parameter. Default: 60 seconds
- enable_parallel_profile_deployment:Deployment of profiles are decoupled from processing of devices at group level for increasing the performance of MCS based on this flag. Default: true
- profile_interval:The frequency to check the changes for profiles. Profiles can be added or modified or deleted. For bulk deployments the values can range from 120-900. Default: 30 seconds
- retry_cycles:The frequency (in intervals) to prioritize profiles that were not applied successfully during the previous reconciliation tasks.Default: 3 (every third cycle)
- (mon_config_service v8.44 and earlier) threads:The number of threads to use when deploying configuration profiles. Each thread is used to deploy configuration profiles to a single probe.Default: 1
- (mon_config_service v9.02) policy_mode_enabled:This parameter decides what sections are displayed in the UMP UI for metrics and alarm definition configuration (for enhanced profiles).
- If the value is true, theMetricssection is displayed in the UI for metrics configuration.
- If the value is false, theMetric Collection and Alarm Definitionsection is displayed for metrics and alarms configuration. TheMetric Collection and Alarm Definitionsection includesMetrics,Alarms, andTime Over Thresholdsections.
- (mon_config_service v9.10)enable_container_support_for_alarm_policy: Lets you enable support for alarm policies for container groups. To enable the support, set the parameter value to true.Default: false