Chapter 4. Resolved issues and known issues

In OpenTelemetry, there is a separate OpenTelemetry instance for each application. These instances share the same configuration, which results in metrics from each application being exported together.

Each OpenTelemetry-enabled application reports and tracks JVM and system metrics, which can affect the performance of your system and increase inefficiency.

This behavior can cause unexpected results in multi-deployment environments where applications are expected to operate in isolation.

A future release is planned to change this behavior to ensure OpenTelemetry metrics collection between deployments and between deployments and the underlying server system.

In Micrometer observability, all applications deployed on the same server instance share a single MeterRegistry. An application can access meters from another application and system meters by using the MeterRegistry.getMeters() method. An application can also remove meters from other applications or system meters by using the MeterRegistry.remove(Meter), MeterRegistry.remove(Meter.Id), or MeterRegistry.clear() methods.

This behavior exists in the current Micrometer implementation and can cause unexpected results in multi-deployment environments where applications are supposed to operate in isolation. A future release is planned to change this behavior to ensure proper metric isolation between deployments and between each deployment and the underlying server system.

Currently, JBoss EAP XP 6.0 does not support multiple deployments that use Micrometer in the same server instance. Support for this configuration is planned to be reconsidered in a future release after the underlying issue is resolved.

There are several non final OpenTelemetry artifacts shipped with JBoss EAP XP 6.0 due to MicroProfile specification requirements:

JBoss EAP XP 6.0 provides limited support for multiple deployments that use the MicroProfile OpenAPI subsystem. Each deployment must either use a different virtual host or configure a distinct, non-standard OpenAPI endpoint path.

Support for using the standard OpenAPI endpoint on the same virtual host is planned to be delivered in a subsequent update release.

In JBoss EAP XP 6.0, when an application sets the mp.health.disable-default-procedures=true configuration property, the server disables the default procedures. However, the server does not reset this state when the application is undeployed. As a result, default procedures remain disabled even when no deployed application defines this property.

This behavior can cause unexpected health check responses in multiple deployment environments.

To enable default procedures, reload the server after undeploying the application that defined mp.health.disable-default-procedures=true.

Support for automatically resetting this configuration property after undeploying the application is planned to be delivered in a subsequent update release.