The JDBC collector allows you to create datasources that query databases, collect and store data from a SQL query, alert on them, and graph them. If you select a Collector type of jdbc (in the datasource General Information section), the form will display JDBC specific attributes section: URL URL is the jdbc url … Continued
The webpage collector can be used to query data from any system via HTTP or HTTPS. Note: The webpage collector supports circular redirects, up to a maximum of 3 redirects. Token substitutions can be used to make the collector generic (Typically, ##WILDVALUE## will be used in Active Discovery datasources, and be replaced with the port … Continued
Overview PowerShell scripts can be integrated into LogicMonitor in order to monitor specific Windows stats which are unavailable from WMI or Perfmon. Windows Setup The most useful way to utilise PowerShell in LogicMonitor is by using remote PowerShell scripts. Some setup in Windows is required to allow this to happen. STEP 1: Open a PowerShell … Continued
The Collector includes dnsjava (dnsjava.org) to allow scripting of DNS based objects. To determine which version of dnsjava is installed in your environment, navigate to the Collector installation folder and verify the version installed: Default library path on Windows – C:\Program Files\LogicMonitor\agent\lib Default path on Linux – /usr/local/logicmonitor/agent/lib See https://github.com/dnsjava/dnsjava for documentation on the version of dnsjava … Continued
The most robust way to call external processes is to use the Groovy method waitForProcessOutput. For example: command=”../bin/ipmiutil sensor -c -N ” + hostname + ” -U “+User+” -P ” +Pass def sout = new StringBuffer() def serr = new StringBuffer() def proc = command.execute() proc.waitForProcessOutput(sout, serr) if(proc.exitValue() == 0) { output=sout.toString() output.eachLine { if (it … Continued
When you create an embedded Groovy script in your LogicMonitor account, keep in mind that it will be run inside the same JVM as your Collector. The guidelines are as follows: Scripts are meant to be light-weight. When integrated into a Datasource, they need to execute within 1 minute. They also must fit within the memory resources of the Collector … Continued
The JMX collector is used to collect data from java applications using exposed MBeans. For issues with configuring JMX collection, see this page. An MBean is identified by the combination of a domain and a list of properties. For example, domain= java.lang, and properties type=Memory, identifies the MBean that reports on memory usage of a … Continued
The SNMP method will start by trying v3, then v2c, then v1 in that order. See Defining SNMP Credentials and Properties for more details. Datasources based on the SNMP Data Collection method primarily use snmpget to access hosts/devices. In some cases where the device has a mulit-instance structure, Active Discovery will use snmpwalk (SNMP GETNEXT requests) to identify the Wildcard … Continued
Overview LogicMonitor allows NetApp data collection via three methods: Performance Data Request XML API Call Note: NetApp storage arrays will also respond to SNMP, and some datasources employ SNMP to collect NetApp data. This article talks only about using the NetApp API to collect data. Performance Data Performance Data Collection makes a perf-object-get-instances request for … Continued
