-
Notifications
You must be signed in to change notification settings - Fork 324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[validation config file ]: command or other way to validate config file #484
Comments
I agree, this would be a great thing to have. It could be a function of the regular exporter, if supplied with a flag it would check the configuration and exit (status code 0 if correct, 1 if incorrect). As the base case, I think this should be a purely offline syntax check. However, given the nature of the exporter, it would be useful to have an extended / online check mode that actually connects to CloudWatch to validate that it can fetch the metrics, dimensions are correct, etc. Iit should not stop at the first error but rather list all (possible) problems. |
Command or other way to validate the configuration file
It will be better to validate the configuration file to detect errors before loading it .
This will allow the user to only load the correct configuration files and not break what is already running
A command to validate the configuration file can be a good solution
The text was updated successfully, but these errors were encountered: