BatchScript Config Monitoring

Last updated - 05 September, 2025

LogicMonitor provides common configuration monitoring modules from Scripted to BatchScript implements to enhance consistency and maintainability. BatchScript Config Monitoring improves module consistency, supports better maintainability, and aligns with platform-wide modernization efforts.

Requirements for Migrating to BatchScript Config Monitoring

You must have LogicMonitor Collector version 36.200 or later to use the BatchScript-based ConfigSources.

Migrating to BatchScript Config Monitoring

If your environment currently uses Scripted ConfigSources, you can import the BatchScript versions without losing historical configuration data.

LogicModules in Package

LogicMonitor’s package for BatchScript Config Monitoring consists of the following LogicModules. For full coverage, ensure that all of these LogicModules are imported into your LogicMonitor platform:

Display Name	Type	Description
Config Batch Metrics	DataSource	Collects metrics on configuration collection success and failure.
ConfigCheck_1_SFTP	PropertySource	Sets auto.config.type.sftp if SFTP-based collection is available.
ConfigCheck_2_SCP	PropertySource	Sets auto.config.type.scp if SCP-based collection is available.
ConfigCheck_3_Exec	PropertySource	Sets auto.config.type.exec if SSH Exec-based collection is available.
Dynamic Configs (Direct Batch)	ConfigSource	Handles dynamic config collection using direct methods. Does not alert by default.
Standard Configs (Direct Batch)	ConfigSource	Collects configs using direct methods and alerts on non-filtered changes.

When setting static datapoint thresholds on the various metrics tracked by this package’s DataSources, LogicMonitor follows the technology owner’s best practice KPI recommendations.