Follow Mike's blog
Archives for the month of: February, 2017


If you use Scheduled Tasks, you probably want to know when they fail. This DataSource uses PowerShell to show all your enabled scheduled tasks and the LastResult code. 0 (zero) means success. Believe it or not, there are ~40 other codes. Microsoft, it it’s infinite wisdom lists them here in hexadecimal but PowerShell shows them as decimal. I will attach the most common conversions. I took advantage of the Discovery Filter feature of LogicMonitor to exclude the typical ~50 that Microsoft includes on most Windows computers and 2 with “Optimize Start Menu” in the name.


  1. Download the DataSource file and add them to your account (Settings > DataSources > Add > From file )
  2. Change the “Applies to” to apply them to the computer(s) that have Scheduled Tasks
  3. Test by making sure expected values show in “Raw Data” tab.

Disclaimer: LogicMonitor tech support cannot officially provide support for this DataSource.



It’s often helpful to know how fast your WAN is performing between various offices. This copies a 10MB file (or specified size) from any collector computer to any target server(s) by specifying a UNC path. To closer approximate real-life users…It automatically creates the test file and fills it with random content each time so it doesn’t get cached and compressed by WAN accelerator appliances.


  1. Download the DataSource file and import it into your account ( Settings > DataSources > Add > From file )
  2. To do the file creation, I used a free utility called DUMMYCMD.exe (download here) and put it on the collector computer in any folder that’s in the path.
  3. On the device tree, select your desired collector and click the blue pull-down menu and click “add monitored instance” for each target to copy to. Fill in the blanks – see example below
  4. Test by looking at the “Raw Data” tab after the first few polls come in.
  5. Change the alert threshold to suit your needs.


  • This requires Windows collector because it’s a PowerShell script.
  • Don’t expect this datasource to be officially supported by LogicMonitor tech support.


The Collector listens on these ports:

162 UDP for SNMP traps
514 UDP for SysLog traps
2055 UDP for Netflow
6343 UDP for Sflow
2056 UDP for jflow

‘within’ the collector:

7211 TCP Watchdog service (sbwinproxy.exe)
7212 TCP Collector Service (java.exe)
7213 TCP Watchdog service (java.exe)
7214 TCP Collector Service (java.exe)
31000 TCP Collector service (java.exe) establishes connection with wrapper.exe
31001+ TCP Watchdog service (java.exe) establishes connection with wrapper.exe

Common outbound ports:

135 TCP for Windows. Unfortunately after initial connection it uses one other port between 1000-65000 (This is decided on the fly but you can lock it down to TCP 24158 or with more clicks you can specify any port)
22 TCP for SSH connections
80 TCP for HTTP
443 TCP for HTTPS
25 TCP for SMTP (email)
161 UDP for SNMP
1433 TCP for Microsoft SQL
1521 TCP for Oracle
3306 TCP for MySQL
5432 TCP for PostgreSQL
Various both for various apps like JMX or other