Early Release Collector 22.084 will be released July 25, 2016.
Note: There is a known WMI issue with this Collector Version that causes certain WMI collection tasks to timeout. We will be releasing a new EA Collector with a fix for this issue soon.
EA 22.084 contains the following:
- Instance Level Properties – LogicMonitor instance level properties (ILPs) allow you to set properties at the datasource instance level, or have them discovered via Active Discovery. ILPs provide you with an additional layer of granularity, and enable you to see detailed information for a particular instance, as well as set instance-level authentication information. You can manually set properties for instances just as you do devices, or you can configure Active Discovery to discover and set instance level properties. Currently, ILP is only supported for WMI & Script Active Discovery methods, and requires v78.
- Added the following option to the Collector’s agent.conf file: reporter.persistent.expire. The option enables configuration of the the amount of time (in minutes) the Collector can cache data, and defaults to 30, which corresponds to 30 minutes of data caching.
- Improved the performance of Collector data caching, which was not working well for Collectors with a heavy monitoring load.
- In some cases, increasing log levels such that a large number of messages were logged was causing the Collector to restart frequently. We’ve optimized how the Collector handles such volumes of log messages to correct for this.
- We’ve added more detail to what is returned by the !apdetail debug command.
- Added Ping RTT Collector support for Internal Services.
- For collector.script log levels of debug and trace, we now log script data collection and active discovery stdout and stderr in the agent/logs directory.
- We’ve added a summary=true|false option for the !tlist debug command. This option can be used to display number of collection tasks for a specific device or collection method, out of the total number of collection tasks.
We’ve added Collector support to discover and update AWS tag values for EC2 instances added into monitoring via Netscan. When the EC2 instances are added into monitoring, we’ll add any associated AWS tags as device properties. Consistent with how properties are typically updated, our Auto Properties subsystem will automatically run and update these properties on a periodic bases. You can additionally trigger a more instantaneous update by manually running Active Discovery for the EC2 device. Note that this does require that you have aws.accesskeyid and aws.accesskey properties set for the discovered devices. We’re working on a way to allow discovered EC2 instances to inherit these credentials if they are already set in your account (e.g. at a group level).
- Internal Service checks weren’t working well for internal address spaces (10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16). We’ve resolved this issue.
- Occasional gaps in data were observed for SNMPv3 data collection tasks relying on SNMP sessions that were shared across devices. The Collector now creates a new SNMP session for every SNMPv3 device.
- Upgraded the Collector’s Maria JDBC Driver to version 1.4.5, to resolve CPU spikes associated with the previous driver version.
- The SSL Certs- datasource wasn’t working correctly for devices that rely on RC4 ciphers. We’ve extended our RC4 cipher support to resolve this.
- Using the API to install a 64 bit Collector on a 32 bit device was displaying as successful, when it should have failed.
- In certain cases, Collectors with Netflow enabled were unable to successfully load Netflow data from disk during initialization.
- Using the Windows Install Shield Wizard to browse for an account the Collector can run under, and then canceling that browse window, previously resulted in a space being prepended to the username. This was resulting in confusion when the space wasn’t deleted, as it caused valid credentials to fail during Collector installation.
- The Add a Device Wizard wasn’t properly identifying devices that only respond to SNMP v3, even if the correct properties were set for the group the device was being added to. This was due to the wizard only checking SNMP v1 and SNMP v2 in those cases.
- Datasources using the webpage collection method and configured to use HTTP 1.0 weren’t always working correctly. This was due to HTTP 1.1 being used when HTTP 1.0 should have been used.
- Setting eventcollector.syslog.enable=false in the Collector configuration has always disabled syslog monitoring, but it did not previously prevent the Collector from listening on the syslog port (port 512). Setting this option now disables syslog monitoring and prevents the Collector from listening on port 512.
- Fixed a WMI data collection issue for Windows Collectors with a monitoring load that included a large number of inactive devices. This issue was introduced in the first 22 EA Collector, and was due to blocked threads for WMI data collection. We’ve optimized our thread allocation for WMI collection tasks to account for this.
- In certain scenarios, Windows Collectors were not successfully caching data. This has been corrected.
In this Article: