Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Configuration validation #75

Open
aadamovich opened this issue Mar 25, 2014 · 2 comments
Open

Configuration validation #75

aadamovich opened this issue Mar 25, 2014 · 2 comments

Comments

@aadamovich
Copy link

It would be benefitial if JMXtrans reported non-valid configuration and invalid property names

@cyrille-leclerc
Copy link
Member

It's a kind of drawback of json over xml. It is very hard to identify the json nodes that are ignored.

I would not want to raise an exception in case of unexpected node because suffixing json node names is a common way to comment blocks in json (json does not have an equivalent for ).

Cyrille

@aadamovich
Copy link
Author

I agree, exception would probably be too much, but a validation notice on debug or warning output will be beneficial. This will help catching misspelled configuration property names. Probably. JSON shema validator can be used for this or some simpler approach.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

2 participants