Creating LogicModules
The Create LogicModule wizard guides you through building new modules directly from LMDA Composer. Create DataSources, ConfigSources, and other module types without leaving the editor.
Prerequisites
Section titled “Prerequisites”| Requirement | Description |
|---|---|
| Portal Connection | You must be connected to a LogicMonitor portal with an active session |
| Write Access | Your account needs permission to create LogicModules in the portal |
Starting the Wizard
Section titled “Starting the Wizard”Access the Create LogicModule wizard from the welcome screen:
-
Close all tabs or open a new LMDA Composer window to see the welcome screen
-
Click Create LogicModule in the Quick Start section
-
The wizard opens with module type selection
Wizard Steps
Section titled “Wizard Steps”Step 1: Module Type
Section titled “Step 1: Module Type”Select the type of LogicModule to create:
Collect numeric metrics from devices. Supports Active Discovery for multi-instance monitoring.
Collect and track configuration data. Alert on config changes or validation failures.
Discover network topology and relationships between resources.
Discover and set device properties automatically.
Collect and parse log data from devices.
Generate events from device data for alerting.
Run diagnostic scripts on-demand or via Diagnostic Rules.
Step 2: Basic Information
Section titled “Step 2: Basic Information”Enter the module identification:
| Field | Required | Description |
|---|---|---|
| Name | Yes | Technical identifier (alphanumeric, underscores, hyphens) |
| Display Name | DataSource/ConfigSource/EventSource only | Human-readable name shown in UI |
Step 3: Script Configuration
Section titled “Step 3: Script Configuration”Configure the scripting options:
| Option | Description |
|---|---|
| Script Language | Choose between Groovy and PowerShell (where supported) |
| Instance Type | Single instance or Multi-instance with Active Discovery (DataSource/ConfigSource only) |
| Batch Script | Enable batch collection for multi-instance modules |
| AD Language | Choose language for Active Discovery script (can differ from collection) |
Step 4: Confirmation
Section titled “Step 4: Confirmation”Review your configuration before creating:
- Module type and name
- Script language selection
- Instance type and AD settings
- Default settings that will be applied
Initialize Local Directory
Section titled “Initialize Local Directory”You can optionally create a local directory structure for the new module:
| Option | Description |
|---|---|
| Initialize Local Directory | When checked, creates a folder with script files on your local disk |
This is useful if you want to:
- Use version control (Git) for your module scripts
- Have local backups of your work
- Work offline and sync later
Click Create Module to create the module in your portal.
Module Type Comparison
Section titled “Module Type Comparison”| Type | Display Name | Collect Interval | AD Support | Script Languages |
|---|---|---|---|---|
| DataSource | Yes | 1-30 min, 1-24 hours | Yes | Groovy, PowerShell |
| ConfigSource | Yes | 1-24 hours | Yes | Groovy, PowerShell |
| TopologySource | No | 30 min - 12 hours | No | Groovy, PowerShell |
| PropertySource | No | On discovery | No | Groovy, PowerShell |
| LogSource | No | 1-30 min, 1-24 hours | No | Groovy only |
| EventSource | No | 1-30 min, 1-24 hours | No | Groovy only |
| DiagnosticSource | No | On-demand | No | Groovy, PowerShell |
Default Settings
Section titled “Default Settings”Each module type is created with sensible defaults:
DataSource Defaults
Section titled “DataSource Defaults”| Setting | Default Value |
|---|---|
| exitCode Datapoint | A default datapoint that captures the script exit code |
| Collection Interval | 5 minutes |
| AppliesTo | false() (won’t match any resources until configured) |
ConfigSource Defaults
Section titled “ConfigSource Defaults”| Setting | Default Value |
|---|---|
| RetrievalCheck | A config check that alerts when configuration cannot be retrieved |
| Collection Interval | 1 hour |
| AppliesTo | false() (won’t match any resources until configured) |
LogSource Defaults
Section titled “LogSource Defaults”| Setting | Default Value |
|---|---|
| Resource Mapping | Default log fields and resource mapping configuration |
| Collection Interval | 5 minutes |
| AppliesTo | false() (won’t match any resources until configured) |
EventSource Defaults
Section titled “EventSource Defaults”| Setting | Default Value |
|---|---|
| Alert Level | Warning |
| Effective Interval | 60 minutes |
| Schedule | 30 minutes |
| AppliesTo | false() (won’t match any resources until configured) |
All Modules
Section titled “All Modules”After Creation
Section titled “After Creation”Once the module is created:
-
The module opens in a new tab, bound to your portal
-
Edit the collection script in the main editor
-
Use Module Details to configure metadata, datapoints, or config checks
-
Test your script with the Run button
-
Commit changes to save back to LogicMonitor
-
Optionally, save to a module directory for local development
Troubleshooting
Section titled “Troubleshooting”Wizard Not Available
Section titled “Wizard Not Available”Creation Fails
Section titled “Creation Fails”Common causes of creation failures:
| Error | Solution |
|---|---|
| Module name already exists | Choose a unique name |
| Permission denied | Check your LogicMonitor role permissions |
| API error | Verify portal connection and try again |