Forrester Total Economic Impactâ„¢ study finds Edwin AI delivered a 313% ROI for composite organization.

Read more

Release Note

EA Collector 40.300

Feature Highlights

  • Custom Authentication Tokens for HTTPS Data Publisher
  • Verification of Windows OS Language During Installation
  • Kafka Clients Version Upgrade

LogicMonitor EA Collector 40.300 is released on June 22, 2026. It is based on EA Collector 40.200 and includes the following additional updates:

Enhancement

Custom Authentication Tokens for HTTPS Data Publisher

LogicMonitor Data Publisher for HTTPS now supports custom tokens to increase compatibility with various endpoints. To use custom tokens, manually add the following new properties to the agent.conf settings:

  • publisher.http.auth.token.prefix —Customizes the prefix appended to the token value in the Authorization request header when using token-based authentication with publisher.http.bearer.token or publisher.http.custom.token. By default, the property is set to Bearer.
    To use a different prefix or send the token value without a prefix, manually add the property to the agent.conf settings and set it to the desired value.

  • publisher.http.auth.token.delimiter—Defines the separator used between the authorization token prefix (from publisher.http.auth.token.prefix) and the token value in the Authorization request header when using token-based authentication (publisher.http.bearer.token or publisher.http.custom.token). By default, the property is set to a single blank space ( ).
    To use a custom separator, manually add the property to the agent.conf settings and set it to the desired value. The property is ignored when publisher.http.auth.token.prefix is not specified.

  • publisher.http.custom.token—Configures a static non-Bearer token for token-based authentication if the agent.publisher.enable.auth is set to true. The token is sent to the Authorization request header and is formatted using the publisher.http.auth.token.prefix and the publisher.http.auth.token.delimiter.
    The Collector first checks for the value set in publisher.http.custom.token. If not found, it checks for the value set in publisher.http.bearer.token, and finally, basic authentication.
    To use this capability, manually add the property to the agent.conf settings and set it to the desired token value.

Enhancement

Verification of Windows OS Language During Installation

LogicMonitor Collector installer for Windows OS now verifies the language of the OS. During installation, if the installer detects a non-English language Windows OS, the system displays a warning message and aborts the installation process.

Enhancement

Kafka Clients Version Upgrade

LogicMonitor Collector has upgraded the version of the following JAR file to apply minor security updates:

Component or Library NameCurrent VersionUpgraded Version
kafka-clients4.0.04.2.0
Resolved Issue

Fixed incorrect case of the InvokeDynamic flag for Groovy from -DGROOVY.TARGET.INDY to -Dgroovy.target.indy in Collector configurations. However, for versions starting with GD Collector 39.004 through EA Collector 40.200, the system automatically runs a Healthcheck script to rectify the InvokeDynamic flag to -Dgroovy.target.indy in Collector configurations.

14-day access to the full LogicMonitor platform