chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Graham (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CHUKWA-527) stronger configuration checking
Date Thu, 30 Sep 2010 03:36:32 GMT

    [ https://issues.apache.org/jira/browse/CHUKWA-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916360#action_12916360
] 

Bill Graham commented on CHUKWA-527:
------------------------------------

+1. It would be nice to have this output also dump out configs that are used and have this
functionality available for each Chukwa component (i.e., Demuxer, Agent, Collector, etc).

> stronger configuration checking
> -------------------------------
>
>                 Key: CHUKWA-527
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-527
>             Project: Chukwa
>          Issue Type: New Feature
>          Components: data collection, documentation
>            Reporter: Ari Rabkin
>            Assignee: Ari Rabkin
>
> Chukwa has many configuration options, and it's easy to mis-set them.  I'd like to contribute
a module for doing stronger static checks of configuration at startup. 
> In particular, this will flag and log cases where:
>   An option is set in the Chukwa config files that is never read by Chukwa.
>   A non-numeric value is used for a numeric parameter, non-boolean value for boolean
parameter, etc.
> The table of options and types is automatically generated and then human-checked. It
should be easy to keep it up to date.
> The changes to the Chukwa codebase should be quite modest: one new Jar, and a handful
of lines to invoke that Jar on startup.
> Does this sound like a thing people would like to see?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message