You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@flume.apache.org by Robert B Hamilton <ro...@gm.com> on 2015/08/19 23:30:47 UTC
JMX for syslog source
Does the syslog source not support jmx monitoring? I find only channel and sink when using syslog.
Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message.
Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may contain confidential and/or privileged material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this message in error, please contact the sender and delete it from your computer.
Re: JMX for syslog source
Posted by Hari Shreedharan <hs...@cloudera.com>.
I think the Syslog TCP source should be deprecated in favor of the
Multiport Syslog Source - that is more stable and gives better performance
too.
Thanks,
Hari
On Wed, Aug 19, 2015 at 2:46 PM, Ashish <pa...@gmail.com> wrote:
> Nope, the Source uses an deprecated class. Can you please file a JIRA for
> this?
>
> The fix is simple. In SyslogTcpSource Line#61, replace the
> CounterGroup usage with SourceCounter and make related changes in
> code. You can refer other Sources for details. Same is applicable for
> SyslogUDPSource.
>
> A patch is greatly appreciated.
>
> On Wed, Aug 19, 2015 at 2:30 PM, Robert B Hamilton
> <ro...@gm.com> wrote:
> > Does the syslog source not support jmx monitoring? I find only channel
> and sink when using syslog.
> >
> >
> > Nothing in this message is intended to constitute an electronic
> signature unless a specific statement to the contrary is included in this
> message.
> >
> > Confidentiality Note: This message is intended only for the person or
> entity to which it is addressed. It may contain confidential and/or
> privileged material. Any review, transmission, dissemination or other use,
> or taking of any action in reliance upon this message by persons or
> entities other than the intended recipient is prohibited and may be
> unlawful. If you received this message in error, please contact the sender
> and delete it from your computer.
>
>
>
> --
> thanks
> ashish
>
> Blog: http://www.ashishpaliwal.com/blog
> My Photo Galleries: http://www.pbase.com/ashishpaliwal
>
Re: JMX for syslog source
Posted by Ashish <pa...@gmail.com>.
Nope, the Source uses an deprecated class. Can you please file a JIRA for this?
The fix is simple. In SyslogTcpSource Line#61, replace the
CounterGroup usage with SourceCounter and make related changes in
code. You can refer other Sources for details. Same is applicable for
SyslogUDPSource.
A patch is greatly appreciated.
On Wed, Aug 19, 2015 at 2:30 PM, Robert B Hamilton
<ro...@gm.com> wrote:
> Does the syslog source not support jmx monitoring? I find only channel and sink when using syslog.
>
>
> Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message.
>
> Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may contain confidential and/or privileged material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this message in error, please contact the sender and delete it from your computer.
--
thanks
ashish
Blog: http://www.ashishpaliwal.com/blog
My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: JMX for syslog source
Posted by Ashish <pa...@gmail.com>.
Flume exposes certain metrics via JMX, instrumentation system doesn't
use CounterGroup class. So if a Source uses it, the counters are not
available via JMX. There are few JIRA's around this with patches.
Hopefully I should be able to spend some time starting next week
towards a few pending JIRA's.
thanks
Ashish
On Sat, Sep 19, 2015 at 4:16 AM, Otis Gospodnetić
<ot...@gmail.com> wrote:
> Hi,
>
> Just curious, what was the original intent? To have something that can
> connect to any JMX host:port and grab the whole contents of JMX and send it
> to ____ via Flume?
>
> Ashish & Hari: https://issues.apache.org/jira/browse/FLUME-2797
>
> Otis
> --
> Monitoring * Alerting * Anomaly Detection * Centralized Log Management
> Solr & Elasticsearch Support * http://sematext.com/
>
>
> On Wed, Aug 19, 2015 at 5:30 PM, Robert B Hamilton <ro...@gm.com>
> wrote:
>>
>> Does the syslog source not support jmx monitoring? I find only channel and
>> sink when using syslog.
>>
>>
>> Nothing in this message is intended to constitute an electronic signature
>> unless a specific statement to the contrary is included in this message.
>>
>> Confidentiality Note: This message is intended only for the person or
>> entity to which it is addressed. It may contain confidential and/or
>> privileged material. Any review, transmission, dissemination or other use,
>> or taking of any action in reliance upon this message by persons or entities
>> other than the intended recipient is prohibited and may be unlawful. If you
>> received this message in error, please contact the sender and delete it from
>> your computer.
>
>
--
thanks
ashish
Blog: http://www.ashishpaliwal.com/blog
My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: JMX for syslog source
Posted by Otis Gospodnetić <ot...@gmail.com>.
Hi,
Just curious, what was the original intent? To have something that can
connect to any JMX host:port and grab the whole contents of JMX and send it
to ____ via Flume?
Ashish & Hari: https://issues.apache.org/jira/browse/FLUME-2797
Otis
--
Monitoring * Alerting * Anomaly Detection * Centralized Log Management
Solr & Elasticsearch Support * http://sematext.com/
On Wed, Aug 19, 2015 at 5:30 PM, Robert B Hamilton <ro...@gm.com>
wrote:
> Does the syslog source not support jmx monitoring? I find only channel and
> sink when using syslog.
>
>
> Nothing in this message is intended to constitute an electronic signature
> unless a specific statement to the contrary is included in this message.
>
> Confidentiality Note: This message is intended only for the person or
> entity to which it is addressed. It may contain confidential and/or
> privileged material. Any review, transmission, dissemination or other use,
> or taking of any action in reliance upon this message by persons or
> entities other than the intended recipient is prohibited and may be
> unlawful. If you received this message in error, please contact the sender
> and delete it from your computer.
>