Hi,
You will probably need to implement a new component with it java client
apis.
Please check camel documentation and several camel books.
Onder
On Tue, 23 Nov 2021 at 00:43, ASHWIN .P.S wrote:
> Hi Team,
>
> We need support to integrate Apache camel with Microsoft Graph API to read
> Outloo
Great, Claus.
I'll investigate it, thanks to pointing the source.
___
Best regards,
Vyacheslav.
Claus Ibsen 29 ноября 2021 г. 20:40:40 написал:
Hi
You cannot expand those, it's hardcoded in the tracer implementation
in Camel 3.x.
You can implement your own tracer via org.apache.camel.spi.Trac
Hi
You cannot expand those, it's hardcoded in the tracer implementation
in Camel 3.x.
You can implement your own tracer via org.apache.camel.spi.Tracer and
plug that into CamelContext.
But an enhancement could be to allow to configure the TRACING_OUTPUT
in the DefaultTracer so you can configure
It generally takes some time for metrics to "show up", depending on the
Prometheus instance configuration:
https://github.com/prometheus-operator/prometheus-operator/blob/787f54b055f797464d5832ace1c7f8318321c87a/Documentation/api.md
That may explain why restarting seems to fix the issue, as it f
Antonin, hi.
I'm getting a problem in my prometheus operator about the podmonitor
discovery
When I start a new integration, it's not discovered by the prometheus
operator! I need to restart the pod operator to my integration to be
discovered and scraped
This is my Prometheus object in k8s:
Hi
Its likely clipped accordingly to:
https://camel.apache.org/manual/faq/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.html
On Mon, Nov 29, 2021 at 1:09 PM Vyacheslav Boyko wrote:
>
> Hi!
>
> 14:07:29.172 [Test worker] INFO org.apache.camel.Tracing - *-->
> [route1 ] [fr
Hi!
14:07:29.172 [Test worker] INFO org.apache.camel.Tracing - *-->
[route1 ] [from[direct://start] ] Exchange[Id:
E2E34A8700E4EE3-, BodyType: ...
14:07:29.176 [Test worker] INFO org.apache.camel.Tracing - [route1
] [marshal[org.apache.camel.model.da] Ex
Yes, there is a possibility. We are customizing the maven repository
to our own...
How can I increase the Camel-k operator log level?
On Mon, Nov 29, 2021 at 6:15 AM Antonin Stefanutti
wrote:
>
> For some reasons, the process that performs the Maven build is killed:
>
> {"level":"info","ts":1637
For some reasons, the process that performs the Maven build is killed:
{"level":"info","ts":1637952361.010027,"logger":"camel-k.builder","msg":"step
failed with error: failure while building project: signal:
killed","step":"github.com/apache/camel-k/pkg/builder/BuildQuarkusRunner","phase":"20","ta
