Request to Add Configuration Verification Option

[agrib-01]

Issue Report: Adding a Config Verification Option to Tempo

Problem:
I am trying to validate the Tempo configuration file before deploying it. However, I have noticed that there is currently no option available to verify the configuration file.

Proposed Solution:
I would like to request the addition of a configuration verification option in Tempo, similar to the "verify-config" option available in Loki, which allows for the validation of configuration syntax before applying the configuration. This option would be very useful to have when deploying and managing Tempo, as it would ensure that the configuration file is valid and reduce the risk of errors during deployment.

Additional Context:
Currently, there is no option available to check the syntax of the configuration file in Tempo, which is available in other related tools such as Loki and Mimir. I believe that adding this option to Tempo would make the tool more versatile and user-friendly.

[joe-elliott]

This is a great idea. I will point out that we have a "CheckConfig" method that will provide warnings on configs that parse correctly but have potentially bad combinations of settings:

https://github.com/grafana/tempo/blob/main/cmd/tempo/app/config.go#L128

I think verify config should parse the config, run it through this method and print out any warnings/errors.

[agrib-01]

Thank you for pointing out the "CheckConfig" method as a potential solution. I appreciate your input and will look into implementing this flag in Tempo. Once I have made the necessary changes, I will create a pull request for review.

[agrib-01]

Hi @joe-elliott,
I've created a PR that allows configuration validation using the flag -config.verify and then terminates the execution.
I would appreciate it if you could review it.

[agrib-01]

Hi,
since the pull request has been merged, I'm closing this issue here.
Thanks again for pointing me to the correct function.