Loading full navigation.

Release Note

EA Collector 41.100

Feature Highlights

  • Execution Parameters for Manual RemediationSource Runs
  • Unified Installer for Collector and Catchpoint Enterprise Node Installation
  • SASL Authentication for Kafka Data Publisher
  • Amazon Java Corretto Version Upgrade
  • Multiple Version Upgrades

LogicMonitor EA Collector 41.100 is released on September 24, 2026. It is based on GD Collector 41.000 and includes the following additional updates:

Enhancement

Execution Parameters for Manual RemediationSource Runs

You can now provide execution parameters when you manually run a RemediationSource from the Resource or Alert page to target a specific process or activity for remediation. The Execution Param tab on the Add RemediationSource page enables you to define parameters that override configured values in the script at run time.

You must enable the Overriding Enabled option to override the default values. You can select text, number, or enum parameter types. Based on the selected type, you must provide parameter values for validation. When you run the RemediationSource, the Run Remediation dialog box enables you to specify values that override the configured values for targeted remediation.

For example, if you have configured a generic script to perform disk cleanup operations on Windows systems, you can define execution parameters and provide specific values or instructions to remove only temporary files. For subsequent runs, you can change the parameter values to perform a different task.

The ability to override configured values using execution parameters is available only when you manually run a RemediationSource from the Resource or Alert page. Automated executions from the Alert page run with the default values set in Execution param.

To access the Execution Param tab, navigate to Settings > LogicModules. In the Add modal, select RemediationSource.

For more information, see RemediationSource Configuration in the product documentation.

Enhancement

Unified Installer for Collector and Catchpoint Enterprise Node Installation

You can now install a LogicMonitor Collector and Catchpoint Enterprise Node on the same machine in a single installation session.

To install the Enterprise Node, you must do the following:

  • Have a LogicMonitor user account with Catchpoint “Create & Modify” permissions for one or both of the Manage Enterprise Nodes And Machines For Client and Manage Enterprise Nodes And Machines For Division settings.

  • Use EA Collector 41.100 or later to access this feature.

To access this feature, navigate to Collector > Add Collector, and toggle the Install Catchpoint enterprise node switch. If you do not see this option, contact your Customer Success Manager.

For more information, see Adding Collector in the product documentation and Enterprise Node Overview from Catchpoint.

Enhancement

SASL Authentication for Kafka Data Publisher

LogicMonitor Data Publisher for Kafka now supports SASL authentication to provide compatibility with Kafka brokers and Kafka-compatible endpoints that require username and password credentials such as, Azure Event Hubs.

To use SASL or SSL authentication, set agent.publisher.enable.auth to true, and kafka.security.protocol to SSL, SASL_SSL or SASL_PLAINTEXT, and manually add the following properties to the agent.conf settings:

  • kafka.sasl.mechanism —Specify the SASL mechanism to authenticate the Kafka producer. Supported values are PLAIN, SCRAM-SHA-256, and SCRAM-SHA-512.

  • kafka.sasl.jaas.config—Raw JAAS configuration string for SASL authentication. If you set this property, the Collector does not build JAAS from kafka.sasl.username and kafka.sasl.password. If you do not set it, both kafka.sasl.username and kafka.sasl.password are required.

  • kafka.sasl.username—Username for SASL authentication when kafka.sasl.jaas.config is not set.

  • kafka.sasl.password—Password for SASL authentication when kafka.sasl.jaas.config is not set.

  • kafka.ssl.use.jvm.default.trust—Controls whether the Kafka producer trusts server certificates using the JVM default truststore. By default, the property is set to false, and the Collector uses the custom truststore (and, for SSL, the keystore) under the publisher certificates directory. Set this property to true when the Kafka endpoint presents a publicly trusted certificate and a custom truststore is not required. For example, Azure Event Hubs with SASL_SSL.

Enhancement

Amazon Java Corretto Version Upgrade

For security updates and improvements, LogicMonitor Collector now supports the latest Amazon JAVA Corretto version 21.0.12.9.1 for Windows and Linux Collectors. It is an upgrade from version 21.0.12.8.1.

Enhancement

Linux Collector Installation Improvement

Added support for Linux Collector installation using Active Discovery domain users in DOMAIN\username format.

Enhancement

Multiple Version Upgrades

LogicMonitor Collector upgrades the following libraries to apply minor security updates:

Library NameCurrent VersionUpgraded Version
netty-all (including its transitive components)
  • netty-codec-stomp
  • netty-codec-http
  • netty-codec-haproxy
  • netty-handler-ssl-ocsp
  • netty-codec-http2
  • netty-codec-xml
  • netty-codec
  • netty-transport-sctp
  • netty-codec-dns
4.1.135.Final4.1.137.Final
Bouncy Castle components
  • bcpkix-jdk18on
  • bcprov-jdk18on
1.841.85
jackson-databind2.18.82.18.9
jetty-server12.1.712.1.11
lz4-java1.10.11.11.1
log4j-api2.25.42.26.1
jsoup1.15.31.23.1
mariadb-java-client2.5.42.7.14
java-allocation-instrumenter3.03.3.5
wildfly-elytron2.7.1.Final2.9.2.Final

14-day access to the full LogicMonitor platform