Deprecation of Coralogix Log4j SDK
Published: February 16, 2026
Effective: June 30, 2026
Deprecation notice
Coralogix will deprecate the Coralogix Log4j SDK on June 30, 2026.
Coralogix Log4j libraries are deprecated in favor of OpenTelemetry logging for Java, which is now the recommended and supported approach for exporting logs and correlating them with traces to Coralogix.
Action is required to ensure continued support and compatibility.
Why this is happening
OpenTelemetry provides a standardized approach for logs, metrics, and traces, including support for bridging logs from common logging frameworks into the OpenTelemetry data model.
What’s affected
Coralogix Log4j appender libraries for Log4j 1.x and Log4j 2.x are being deprecated.
These libraries may currently be used in:
- Java services using Log4j where Coralogix appenders are configured in Log4j configuration files
- Applications that configure Coralogix-specific credentials inside Log4j appender configuration
- Build pipelines that package Coralogix Log4j appender dependencies
After the effective date, these SDKs will no longer be supported or maintained.
What you need to do
Migrate to OpenTelemetry logging for Log4j
Replace Coralogix Log4j SDK appenders with an OpenTelemetry-based approach and export via OTLP.
What will happen after June 30, 2026?
- The Coralogix Log4j SDK will no longer be supported.
- No bug fixes, updates, or security patches will be provided.
- Compatibility with newer Log4j versions is not guaranteed.
- Support requests related to the deprecated SDK may be declined.
- Existing applications may continue to function, but migration is strongly recommended.
Need help?
Our team is here to help you migrate smoothly.
Reach out via our 24/7 in-app support or contact your Technical Account Manager, and we’ll guide you through the transition step by step.