Send Liberty HTTP access logs to OpenTelemetry using MicroProfile Telemetry 2.0 in 25.0.0.5
The 25.0.0.5 release introduces support for collecting Liberty HTTP access logs with MicroProfile Telemetry 2.0, enabling integration with OpenTelemetry alongside existing runtime and application log sources.
In Open Liberty 25.0.0.5:
View the list of fixed bugs in 25.0.0.5.
Check out previous Open Liberty GA release blog posts.
Develop and run your apps using 25.0.0.5
If you’re using Maven, include the following in your pom.xml
file:
<plugin>
<groupId>io.openliberty.tools</groupId>
<artifactId>liberty-maven-plugin</artifactId>
<version>3.11.3</version>
</plugin>
Or for Gradle, include the following in your build.gradle
file:
buildscript {
repositories {
mavenCentral()
}
dependencies {
classpath 'io.openliberty.tools:liberty-gradle-plugin:3.9.3'
}
}
apply plugin: 'liberty'
Or if you’re using container images:
FROM icr.io/appcafe/open-liberty
Or take a look at our Downloads page.
If you’re using IntelliJ IDEA, Visual Studio Code or Eclipse IDE, you can also take advantage of our open source Liberty developer tools to enable effective development, testing, debugging and application management all from within your IDE.
Send Liberty HTTP access logs to OpenTelemetry using MicroProfile Telemetry 2.0
MicroProfile Telemetry 2.0 (mpTelemetry-2.0
) enables OpenTelemetry to collect and export traces, metrics, and logs.
You can now use the mpTelemetry-2.0
feature to collect Liberty HTTP access logs to OpenTelemetry. This new log source is in addition to the previously available Open Liberty runtime log sources (messages, traces, ffdcs, audit) and application logs generated by the java.util.logging
(JUL) API.
To enable the MicroProfile Telemetry 2.0 feature to collect HTTP access logs, enable the feature and configure the httpEndpoint
and optionally the httpAccessLogging
configuration elements. Include the new accessLog
value in the source
attribute of the mpTelemtry
configuration element. Also set the accessLogFields
attribute to default
or logFormat
for the mpTelemetry
configuration element, as shown in the following server.xml
example:
<featureManager>
<feature>mpTelemetry-2.0</feature>
...
</featureManager>
<httpAccessLogging id="accessLogging" logFormat='%h %u %{t}W "%r" %s %b %D %{R}W'/>
<httpEndpoint id="defaultHttpEndpoint" accessLoggingRef="accessLogging" httpPort="9080" httpsPort="9443"/>
<mpTelemetry accessLogFields="logFormat" source="message,trace,ffdc,accessLog"/>
Notable bugs fixed in this release
We’ve spent some time fixing bugs. The following sections describe just some of the issues resolved in this release. If you’re interested, here’s the full list of bugs fixed in 25.0.0.5.
-
[PH66379] Not able to config Liberty 25.0.0.3 + Java 21 with FIPS 140-2
-
WLP version 25.0.0.3 start up intermittently fails with AuthCacheImpl NPE
-
Unclear how to correctly configure library element’s folder and path
-
Enhance the behaviour of ignoreWriteAfterCommit property to more closely mimic tWAS behaviour
New and updated guides since the previous release
As Open Liberty features and functionality continue to grow, we continue to add new guides to openliberty.io on those topics to make their adoption as easy as possible. Existing guides also receive updates to address any reported bugs/issues, keep their content current, and expand what their topic covers.
Get Open Liberty 25.0.0.5 now
Available through Maven, Gradle, Docker, and as a downloadable archive.