BatchScript Config Monitoring
Last updated - 15 May, 2026
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.
BatchScript Config Monitoring uses ConfigCheck PropertySources to set config.type based on successful validation of commands. Because this detection is based on partial command success, it does not reflect full configuration requirements. For example, show version can succeed in SSH Exec mode, while show running-config fails due to required privilege escalation. In this case, config.type.exec is assigned even though interactive access is required.
BatchScript does not assume privilege escalation by default. Interactive mode requires explicitly configured credentials.
Note: If full configuration collection fails, manually set config.type.'protocol'config.type.interactive
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.
Recommendation: After verifying that the BatchScript modules are functioning correctly, disable the following corresponding Scripted ConfigSources to avoid duplicate data collection and alerts:
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.
Recommendation: As necessary, adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Static Thresholds for Datapoints.
