[jira] [Commented] (FLUME-1817) Monitoring configuration should be done in the config file and not per jvm switches (-D atm)

["Mingjie Lai (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLUME-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543712#comment-13543712 ] 

Mingjie Lai commented on FLUME-1817:
------------------------------------

Right. Currently we can only have one monitor type, either http or ganglia, for flume. 

AFAIK, hdfs always provide metrics through http, so ppl can always use curl to query any metrics. In the meanwhile, users can configure to enable ganglia, or jmx in addition. 
                
> Monitoring configuration should be done in the config file and not per jvm switches (-D atm)
> --------------------------------------------------------------------------------------------
>
>                 Key: FLUME-1817
>                 URL: https://issues.apache.org/jira/browse/FLUME-1817
>             Project: Flume
>          Issue Type: Improvement
>          Components: Configuration
>    Affects Versions: v1.3.0
>            Reporter: Alexander Alten-Lorenz
>
> We have no possibility to add more as one monitoring service to flume. In some cases it could be helpful to have more as one monitoring system (jmx and ganglia or nagios as example). 
> We should move the monitoring configuration into the config file, configurable per identifier:
> Example:
> monitoring1.service.name=ganglia
> monitoring1.host.name=FQDN
> monitoring1.host.port=PORT
> monitoring1.username=USERNAME
> monitoring1.password=PASSWORD (salted? md5'ed?)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira