camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sashika <sashik...@gmail.com>
Subject Re: Camel Context Metrics
Date Tue, 16 Aug 2016 15:27:51 GMT
In addition to what Vitalii mentioned you can use control bus to obtain
route stats in a more EIP friendly manner. This is also a good way the
application to access the stats as you requested in your question.

On Aug 16, 2016 20:32, "Rajith Muditha Attapattu" <rajith77@gmail.com>
wrote:

> Thanks Vitalii
>
> On Tue, Aug 16, 2016 at 10:16 AM, Vitalii Tymchyshyn <vit@tym.im> wrote:
> > Just a note. If you are in same JVM and has CamelContext objects ready,
> you
> > can always access stats data
> > with org.apache.camel.CamelContext#getManagedCamelContext. You don't
> need
> > JMX to do this.
> >
> > Best regards, Vitalii Tymchyshyn
> >
> > Пн, 15 серп. 2016 о 11:30 Rajith Muditha Attapattu <rajith77@gmail.com>
> > пише:
> >
> >> Hey All,
> >>
> >> I'm aware of the hawt.io plugin that connects to a Camel Context and
> >> pulls info via JMX.
> >>
> >> For performance reasons, we are looking at how an application (that
> >> contains one or more Camel Context) wants to push route metrics to an
> >> external source. We have several of those apps, which is why
> >> connecting to all of them via a hawtio console want scale well.
> >>
> >> Whats the best way to gather the metrics at the application level?
> >>
> >> (After which it will be sent to an external source like elastic search)
> >>
> >>
> >> 1. Access the info from JMX (programatically)
> >>
> >>
> >> 2. Implement some sort of Listener interface to get notified.
> >>
> >>
> >> I prefer the latter, but the former is fine as well.
> >>
> >> --
> >> Regards,
> >>
> >> Rajith Muditha Attapattu
> >>
>
>
>
> --
> Regards,
>
> Rajith Muditha Attapattu
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message