Failures and exceptions should be identified via logs. Camel will log
those. You shouldn't have enough of them to warrant metrics.
Premethius is a metrics system. JMX is just a to access things in the jvm.
Micrometer will do some of what JMX will do. Camel is going to use
micrometer to create the
I would like to monitor Camel routes and track down issues on routes that
are failing or throwing exceptions.
For folks out there using Camel+Micrometer+Prometheus to gather metrics:
can you get metrics related to success/failure rates of Camel routes in
Prometheus? Can you use the metrics to iden
Ah you mean that Camel OSGi always looking for service first before falling
back to bean located in the same container as the camel context (spring or
blueprint) ?
If so, we have to improve camel-core-osgi in the lookup to add an option
defining the bean resolution order.
Regards
JB
> Le 1 ju
Hi JB
I would, if that was the issue.
However in all the CamelContexts I'm only using regular beans, not calling an
OSGi service.
Ideally there should be a way to tell Camel to not look into the OSGi registry
when resolving bean names. But seems hardcoded?
- Martin
On 29.06.2020 09:34, Jean-
Hi Gerald,
I am not sure you can do that as it is part of the data
header (metadata), but I think for any processing purpose you can have your own
timestamp.
Regards,
Vikas
-Original Message-
From: Gerald Kallas [mailto:catsh...@mailbox.org]
Sent: 01 July 2020 13:09
Thanks Vikas.
Is there a way to specify a dedicated offset timestamp?
Best
- Gerald
> Vikas Jaiswal hat am 01.07.2020 03:06 geschrieben:
>
>
> seekTo allows you to specify 'beginning' or 'end'.
>
> Regards,
> Vikas
>
> -Original Message-
> From: Gerald Kallas [mailto:catsh...@mail
