Configure the MetricsFeature through application.properties

[manubell]

Currently to enable metrics for quarkus-cxf it is required to use the specific feature module quarkus-cxf-rt-features-metrics and configure reference a framework class for each client or endpoint that wants to enable it.

quarkus.cxf.client.MYCLIENT.features=io.quarkiverse.cxf.metrics.QuarkusCxfMetricsFeature

Other libraries (Hibernate, Log, Scheduler, GraphQL, etc...) typically have a boolean parameter like
quarkus.EXTENSION.metrics.enabled

Would be great to have a similar parameter for quarkus-cxf. This would reduce repetitive boilerplate in the application.properties and make it very straightforward to add. Similar treatment to what was done for logging recently in #1102

Could be global as quarkus.cxf.metrics.enabled
Or separated for client and endpoint quarkus.cxf.client.metrics.enabled and quarkus.cxf.endpoint.metrics.enabled if needed.

[ppalaga]

The change is underway in #1161
The MetricsFeature is created internally and enabled by default for all clients and service endpoints, as long as the quarkus-cxf-rt-features-metrics extension is in class path. It can be disabled globally via quarkus.cxf.metrics.enabled-for and per client via quarkus.cxf.client."clients".metrics.enabled or per service endpoint via quarkus.cxf.endpoint."endpoints".metrics. I did it similarly for the new OpenTelemetry extension. Would this fulfill your needs @manubell?

[manubell]

Sounds great. Thanks for the change!