[
https://issues.apache.org/jira/browse/CAMEL-21384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893423#comment-17893423
]
Pasquale Congiusti commented on CAMEL-21384:
--------------------------------------------
That's correct. It is something configurable, but it requires the user to do
that ahead of time. And, on the "consuming" side, it requires the tool to know
that information as well. It would be cool if we can have some mechanism to
take care to default to some camel standard, instead of a given runtime
standard. This problem here is specific to metrics exposure, but, we have a
similar situation for health, logging and other tuning that may be consumed by
third parties.
> [camel-micrometer] Analyse the possibility to harmonize the metrics endpoint
> ----------------------------------------------------------------------------
>
> Key: CAMEL-21384
> URL: https://issues.apache.org/jira/browse/CAMEL-21384
> Project: Camel
> Issue Type: Improvement
> Affects Versions: 4.x
> Reporter: Pasquale Congiusti
> Assignee: Pasquale Congiusti
> Priority: Minor
>
> I've been testing the Camel-micrometer component with the different runtimes
> we have. So far, each of the runtime requires a different set of
> configuration and it exposes the metrics in a different endpoint:
> {code}
> ######## Camel MAIN
> (application.properties)
> camel.server.enabled=true
> camel.server.metricsEnabled=true
> camel.metrics.enabled=true
> $ camel run test.yaml application.properties
> URL --> http://localhost:8080/q/metrics
> ######## Camel QUARKUS
> Blank application.properties
> $ camel run test.yaml --runtime quarkus --dep
> mvn:io.quarkus:quarkus-micrometer-registry-prometheus --dep camel-micrometer
> URL --> http://localhost:8080/q/metrics
> ######## Camel SPRINGBOOT
> (application.properties)
> management.endpoints.web.exposure.include=prometheus
> $ camel run test.yaml application.properties --runtime spring-boot --dep
> mvn:io.micrometer:micrometer-registry-prometheus --dep camel-micrometer
> URL --> http://localhost:8080/actuator/prometheus
> {code}
> We should understand if it is feasible to harmonize somehow the configuration
> to be able to spit the metrics to the same endpoint OOTB.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
