list_netscans
List all network discovery scans to audit configurations, review schedules, and troubleshoot device auto-discovery issues.
Instructions
List all network discovery scans (NetScans) in LogicMonitor (LM) monitoring.
Returns: Array of netscans with: id, name, description, scan method (nmap/script/ICMP/SNMP), schedule, target networks (IP ranges/subnets), collector, last run time, resource/device discovered.
What are netscans: Automated network discovery that finds resource/device on your network and adds them to monitoring. Instead of manually adding resource/device one-by-one, netscan automatically discovers and onboards resource/device based on IP ranges or subnets.
When to use:
Audit existing discovery configurations
Check which networks are being scanned
Review netscan schedules
Troubleshoot why resource/device not auto-discovered
Find netscan IDs for modifications
How netscans work: Scheduled job → Scan network range (e.g., 192.168.1.0/24) → Find live resource/device → Check if already monitored → If new, add to LogicMonitor → Apply resource/device properties and datasources → Begin monitoring
NetScan methods:
nmap: Network mapper scan (comprehensive, detects OS, ports, services)
ICMP Ping: Simple ping sweep (fastest, basic reachability)
SNMP Walk: Query SNMP-enabled resource/device (network gear, servers with SNMP)
Script: Custom discovery logic (cloud APIs, CMDBs, etc.)
AWS/Azure/GCP: Cloud auto-discovery via APIs
Common use cases:
Data center discovery: Scan 10.0.0.0/16 network, auto-add all servers
Cloud auto-discovery: Scan AWS account, add all EC2 instances daily
Branch office monitoring: Scan remote office subnets, discover network resource/device
Dynamic infrastructure: Auto-discover containers, VMs as they spin up
Example NetScan configurations:
"Production Servers" - Scan 192.168.1.0/24 every 6 hours via nmap
"AWS EC2 Discovery" - Query AWS API every hour for new instances
"Network resources/Devices" - SNMP walk 10.0.0.0/8 daily for routers/switches
Workflow: Use this tool to review netscans, then "get_netscan" for detailed configuration including filters and resource/device properties.
Important: A negative "total" value in the response indicates incomplete results. Use pagination (size/offset parameters) or set autoPaginate: true to retrieve all items.
Related tools: "get_netscan" (configuration details), "create_netscan" (set up auto-discovery), "run_netscan" (trigger manual scan).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| size | No | Number of results per page (default: 50, max: 1000). | |
| offset | No | Starting offset for pagination (default: 0). Use this to skip a specific number of results. | |
| autoPaginate | No | Automatically fetch all pages (default: false). When true, fetches all results across multiple pages. When false, returns only the requested page. Use false for large result sets to avoid long response times. | |
| filter | No | Filter expression using LogicMonitor query syntax. Examples: name:*prod*, displayName~*server*, id>100, hostStatus:normal. Available operators: : (equals), ~ (includes), !: (not equals), !~ (not includes), >: (greater than or equals), <: (less than or equals), > (greater than), < (less than). Multiple conditions: Use comma (,) for AND, use || for OR. Do NOT use &&. | |
| fields | No | Comma-separated list of fields to include in response. Examples: "id,displayName,hostStatus" or use "*" for all fields. Omit this parameter to receive a curated set of commonly used fields. |