[
https://issues.redhat.com/browse/WFLY-14151?page=com.atlassian.jira.plugi...
]
Jeff Mesnil updated WFLY-14151:
-------------------------------
Description:
The microprofile-health-smallrye subsystem is provided by the wilfdfly galleon-pack.
However its logical inclusion is in the microprofile feature pack
(org.wildfly:wildfly-mp-feature-pack-galleon-common) which provides features for
MicroProfile.
We should move the subsystem (and extension) to this feature pack.
However, the base WildFly server is still expected to provide "base" healthiness
information (to determine when the application server is ready to serve requests) that
can be consumed out of the box by a container platform such as Kubernetes.
I propose to introduce a simple "health" subsystem (without any external
dependencies) that provides a HTTP endpoints to probe the server healthiness.
The microprofile-health-smallrye subsystem will be refactored to "plug" in the
same HTTP endpoint and overrides the base health endpoint and provide the full features of
MicroProfile health
was:
The microprofile-metrics-smallrye subsystem is provided by the wilfdfly galleon-pack.
However its logical inclusion is in the microprofile feature pack
(org.wildfly:wildfly-mp-feature-pack-galleon-common) which provides features for
MicroProfile.
We should move the subsystem (and extension) to this feature pack.
However, the base WildFly server is still expected to provide "base" metrics
(for the WildFly management model and the JVM) that can be consumed out of the box.
I propose to introduce a simple "metrics" subsystem (without any external
dependencies) that exposes the WildFly management model and the JVM (using JMX) to the
/metrics endpoint (on the management port) with the Prometheus format.
The microprofile-metrics-smallrye subsystem will be refactored to "plug" in the
same HTTP endpoint and overrides the base metrics endpoint and provide the full features
of MicroProfile metrics (application metrics, JSON output, etc.)
Introduce a base "health" subsystem and move
microprofile-health to the microprofile feature-pack
-------------------------------------------------------------------------------------------------
Key: WFLY-14151
URL:
https://issues.redhat.com/browse/WFLY-14151
Project: WildFly
Issue Type: Feature Request
Components: MP Metrics
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Priority: Major
Fix For: 22.0.0.Beta1
The microprofile-health-smallrye subsystem is provided by the wilfdfly galleon-pack.
However its logical inclusion is in the microprofile feature pack
(org.wildfly:wildfly-mp-feature-pack-galleon-common) which provides features for
MicroProfile.
We should move the subsystem (and extension) to this feature pack.
However, the base WildFly server is still expected to provide "base"
healthiness information (to determine when the application server is ready to serve
requests) that can be consumed out of the box by a container platform such as
Kubernetes.
I propose to introduce a simple "health" subsystem (without any external
dependencies) that provides a HTTP endpoints to probe the server healthiness.
The microprofile-health-smallrye subsystem will be refactored to "plug" in the
same HTTP endpoint and overrides the base health endpoint and provide the full features of
MicroProfile health
--
This message was sent by Atlassian Jira
(v7.13.8#713008)