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.
