LogicMonitor seeks to disrupt AI landscape with $800M strategic investment at $2.4B valuation to revolutionize data centers.

Learn More

EA Collector 36.300

Last updated on 03 October, 2024

Feature Highlights

  • Improvements to the nonrootenhancements.sh file
  • Improvements to the Ping Functionality
  • Addition of Resource Property

LogicMonitor EA Collector 36.300 is released on October 03, 2024. It is based on the EA Collector 36.200 and includes the following additional updates.

Enhancement

Improvements to the nonrootenhancements.sh file

On the Linux platform, the non-root user under which the collector is installed needs privileges to start and stop the collector services (Watchdog and Agent). Up to EA Collector 29.106, the collector installer will edit the /etc/sudoers file to give privilege to non-root user. As per the current design, LogicMonitor has a binary CollectorServiceController which has the owner as root and the setuid flag is enabled for this binary. This allows a user to run that file or program with the permission of the owner of that file. However, you can still follow the older method of manually editing the sudoers file by running the script and passing downgrade as argument. The command is nonroot_enhancements.sh downgrade.

Enhancement

Added Resource Property

To standardize metadata value attached to logs, LogicMonitor has added tags that define the resource type. LogicMonitor has added the resource property predef.externalResourceType as the metadata with key “_resource.type” for Syslog and SNMP trap logs through the agent.conf flow. To add the _resource.type metadata through LogSource log fields, add LM Property(Token) as the method, _resource.type as the key, and ##predef.externalResourceType## as the value.

Enhancement

Improvements to the HTTPS Data Publisher

LogicMonitor has added a default capability to redirect http request in HTTPS Data Publisher when it receives the 3xx error code in the response.

Enhancement

Improvements to the Ping Functionality

If you find any data gaps in Ping, SNMP, or Script tasks, you can now manually add the collector.fsmtask.termination.enable property to the agent.conf settings and set its value to true. By default, this property is not explicitly available and is set to false. When false, the FSMTask for the collection types PING, SNMP, and Script are ignored if a previous task is running. This may result in data gaps. To avoid this, you can set the value to true.

Resolved Issue

Fixed an issue where the debug window command !nslookup failed to fetch the hostname of some internal IPs (the internal IPs which did not have hostname associated with them). To get the result, the !nslookup performed reverse lookup and fetched the PTR records associated with the IP address.

Resolved Issue

Upgraded version of the following file due to minor security updates.

File/Component NameCurrent VersionUpgraded Version
Amazon Corretto Java11.0.23.9.111.0.24.8.1