Skip to content

LogicModule Search

LogicModule Search provides powerful search capabilities across all scripts and datapoints in your portal’s LogicModules.

MethodAction
Welcome ScreenClick Search LogicModules on the welcome screen
Command PalettePress Ctrl+Shift+P and type “Search”
Keyboard ShortcutPress Cmd+K, S to open directly

Search dialog showing results grouped by module type

Search within module script content:

  • Collection scripts
  • Active Discovery scripts
  • Pre-scripts
  • PropertySource scripts
  • ConfigSource scripts

Find code patterns, function calls, variable names, or any text within scripts.

Toggle between modes using the tabs at the top of the search dialog.


SubstringExactRegex
TypeBehaviorExample
SubstringPartial match anywherehost matches hostname, hostProps
ExactWhole word match onlyhost won’t match hostname
RegexRegular expression patternhost\w+ matches hostname, hostProps

Toggle case sensitivity in the search options:

  • Case Insensitive (default) – “Host” matches “host”, “HOST”
  • Case Sensitive – Only exact case matches

Filter search to specific module types:

DataSource ConfigSource EventSource PropertySource TopologySource LogSource DiagnosticSource

Select multiple types to include, or none to search all module types.


Results are grouped by module type, then by module:

DataSource (12 matches)
├── Module_Name_1 (3 matches)
│ ├── AD Script - Line 45
│ └── Collection Script - Line 12, 78
├── Module_Name_2 (1 match)
│ └── Collection Script - Line 156
ConfigSource (5 matches)
└── Config_Module_1 (5 matches)
└── Script - Lines 23, 45, 67, 89, 101

Click a result to see the script with matches highlighted:

  • Monaco editor with syntax highlighting
  • Matching lines highlighted in yellow
  • Jump to match buttons for navigation
  • Context lines around each match

From search results, you have two options:

ActionResult
LoadOpens in new module-bound tab (for editing and committing)
NewOpens as freeform tab (for reference or experimentation)

Shows datapoints matching your query:

DataSource_Name
├── cpuUsage (alert: >, threshold: 90)
├── cpuIdle (alert: <, threshold: 10)
└── cpuCount (no alert)

Results show how the datapoint matched your query:

  • Name match — Query found in the datapoint name
  • Description match — Query found in the datapoint description

This helps you quickly identify why a result appeared and focus on the most relevant matches.

Click a datapoint result to view:

FieldDescription
NameDatapoint identifier
TypeGauge, counter, derive
Alert ExpressionThreshold configuration
DescriptionDocumentation text
Post-ProcessorTransformations

Search results include direct links to view the module on LogicMonitor Exchange when available. Click the icon to open the module in LMX.


LogicModule Search uses a local index for fast searching across your portal.

The status bar shows:

  • Last indexed: When the index was built
  • Module count: Number of indexed modules
  • Index age: Time since last update

The index builds automatically on first search. To manually rebuild:

  1. Click Rebuild Index in the search dialog

  2. Wait for indexing to complete (progress shown)

  3. Index is cached for future sessions


When using Regex mode:

PatternMatches
println.*hostnamePrint statements with hostname
def\s+\w+\s*=Variable definitions
Snmp\.(get|walk)SNMP operations
\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}IP addresses
hostProps\.get\(Host property access

Remember to escape regex special characters:

  • \. for literal period
  • \( for literal parenthesis
  • \[ for literal bracket

For portals with many modules:

  1. Use module type filters to narrow scope
  2. Be specific with search terms
  3. Use exact match when possible
  4. Rebuild index if search seems slow
  1. Start broad, then refine with additional terms
  2. Use regex for complex patterns
  3. Filter by module type early
  4. Check index age before searching

  • Finding Examples — Search for Snmp.walk with Substring match to find SNMP walk examples across all modules.
  • Locating Specific Code — Search for hostProps.get("custom.property") with Exact match to find all uses of a specific property.
  • Auditing Patterns — Use Regex like old_deprecated_function\( to find modules needing updates.
  • Datapoint Discovery — Switch to Datapoint Search and enter “CPU” to find all CPU-related datapoints and their alert configs across all DataSource types.