[jira] [Assigned] (CAMEL-21452) camel-test-infra: decouple the infrastructure from the testing API
[
https://issues.apache.org/jira/browse/CAMEL-21452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Mariani reassigned CAMEL-21452:
Assignee: Federico Mariani
> camel-test-infra: decouple the infrastructure from the testing API
> --
>
> Key: CAMEL-21452
> URL: https://issues.apache.org/jira/browse/CAMEL-21452
> Project: Camel
> Issue Type: Task
> Components: camel-test-infra
>Affects Versions: 4.9.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Federico Mariani
>Priority: Major
> Fix For: 4.10.0
>
>
> It turns out that the test infrastructure management code on the test-infra
> could be useful in multiple other scenarios (i.e.: for Camel JBang). However,
> there's a small set of classes that are bound to the test API used by Camel.
> These APIs would make re-purposing the test infra harder and inelegant for
> users of that code.
> It should be relatively simple to decouple this API (high-level steps,
> details may vary slightly):
> 1. Split
> {{{color:#00}org.apache.camel.test.infra.common.services{color}.TestService}}
> in 2 parts: one named {{InfrastructureService}} for the infrastructure code
> (containing {{{}registerProperties{}}}, {{{}initialize{}}}, {{shutdown}} and
> {{{}close{}}}) and another retaining the {{TestService}} name (containing the
> {{beforeAll}} and {{afterAll}} callbacks from JUnit's
> {{{}BeforeAllCallback{}}}, {color:#00}{{AfterAllCallback}}
> interfaces){color}
> {color:#00}2. Rename the existing {{Service}} to
> {{TestService}} (i.e.: {{{}ElasticSearchTestService{}}}) and make sure
> it implements the {{TestService}} API{color}
> {color:#00}3. Create a new Service and make sure it DOES NOT
> implement the {{TestService}} API
> {color}
> {color:#00}4. Move the infrastructure code to {{src/main}}{color}
> {color:#00}5. Keep the Camel-specific test infra code (i.e.:
> TestService) within {{src/test}}{color}
>
> Repeat for all services in the test-infra.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21456) Camel-Jbang Kubernetes Plugin Ingress add TLS
[ https://issues.apache.org/jira/browse/CAMEL-21456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaelle Fournier reassigned CAMEL-21456: --- Assignee: Gaelle Fournier > Camel-Jbang Kubernetes Plugin Ingress add TLS > - > > Key: CAMEL-21456 > URL: https://issues.apache.org/jira/browse/CAMEL-21456 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 4.x >Reporter: Gaelle Fournier >Assignee: Gaelle Fournier >Priority: Minor > > Camel jbang kubernetes plugin trait Ingress does not yet allow for > configuration of TLS, as is available in CK > ([https://camel.apache.org/camel-k/2.5.x/traits/ingress.html).] > The Ingress model class is already up to date. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (CAMEL-21462) [camel-observability-services] Include more components
[ https://issues.apache.org/jira/browse/CAMEL-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-21462 started by Pasquale Congiusti. -- > [camel-observability-services] Include more components > -- > > Key: CAMEL-21462 > URL: https://issues.apache.org/jira/browse/CAMEL-21462 > Project: Camel > Issue Type: Improvement >Affects Versions: 4.9.0 >Reporter: Pasquale Congiusti >Assignee: Pasquale Congiusti >Priority: Major > Fix For: 4.10.0 > > > With CAMEL-21384 we have introduced a new adapter component, > camel-observability-services. The first MVP exposes metrics. We need to > include more component to be complete: > * Opentelemetry > * Health > * Management -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (CAMEL-21384) [camel-micrometer] Analyse the possibility to harmonize the metrics endpoint
[
https://issues.apache.org/jira/browse/CAMEL-21384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pasquale Congiusti closed CAMEL-21384.
--
Fix Version/s: 4.9.0
(was: 4.10.0)
Resolution: Fixed
Fixed by introducing a new component, camel-observability-services, whose goal
is to normalize the observability configuration among the different runtimes.
> [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
> Fix For: 4.9.0
>
>
> 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)
[jira] [Created] (CAMEL-21462) [camel-observability-services] Include more components
Pasquale Congiusti created CAMEL-21462: -- Summary: [camel-observability-services] Include more components Key: CAMEL-21462 URL: https://issues.apache.org/jira/browse/CAMEL-21462 Project: Camel Issue Type: Improvement Affects Versions: 4.9.0 Reporter: Pasquale Congiusti Assignee: Pasquale Congiusti Fix For: 4.10.0 With CAMEL-21384 we have introduced a new adapter component, camel-observability-services. The first MVP exposes metrics. We need to include more component to be complete: * Opentelemetry * Health * Management -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21463) Camel-jbang while running the process in background unable to access log if the process start fails with errors
Vidhya Sagar Jeevendran created CAMEL-21463: --- Summary: Camel-jbang while running the process in background unable to access log if the process start fails with errors Key: CAMEL-21463 URL: https://issues.apache.org/jira/browse/CAMEL-21463 Project: Camel Issue Type: Bug Components: camel-jbang Affects Versions: 4.8.1, 4.8.0 Reporter: Vidhya Sagar Jeevendran When I run camel integrations with jbang in background and later fetch log using "camel log" I am able to access the log only when the process has started successfully. But when it fails with some error, the log is empty and I am unable to find the failure reason. -- This message was sent by Atlassian Jira (v8.20.10#820010)
