[jboss-jira] [JBoss JIRA] (WFLY-13050) metrics should be optional in observability layer

[Jean Francois Denise (Jira)]

     [ https://issues.redhat.com/browse/WFLY-13050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean Francois Denise updated WFLY-13050:
----------------------------------------
    Description: 
With the introduction of microprofile, one could provision both cloud-server,microprofile and exclude any microprofile-* layer.
config and metrics being not optional in observability, they can't be excluded from cloud-server although they can with other server (jaxrs, datasources). 
config is required by health, so can't be made optional.

So to offer enough flexibility (eg: exclude metrics but provision health) and an aligned experience across the server layers, metrics should be optional in observability.
 


  was:
With the introduction of microprofile, one could provision both cloud-server,microprofile and exclude any microprofile-* layer.
config and metrics being not optional in observability, they can't be excluded from cloud-server although they can with other server (jaxrs, datasources).  This could be solved by excluding observability along with metric/config but in this case health would be excluded too.

So to offer enough flexibility (eg: exclude config but provision health) and an aligned experience across the server layers, config and metrics should be optional in observability.
 




> metrics should be optional in observability layer
> -------------------------------------------------
>
>                 Key: WFLY-13050
>                 URL: https://issues.redhat.com/browse/WFLY-13050
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: Build System
>            Reporter: Jean Francois Denise
>            Assignee: Jean Francois Denise
>            Priority: Major
>
> With the introduction of microprofile, one could provision both cloud-server,microprofile and exclude any microprofile-* layer.
> config and metrics being not optional in observability, they can't be excluded from cloud-server although they can with other server (jaxrs, datasources). 
> config is required by health, so can't be made optional.
> So to offer enough flexibility (eg: exclude metrics but provision health) and an aligned experience across the server layers, metrics should be optional in observability.
>  



--
This message was sent by Atlassian Jira
(v7.13.8#713008)