Print final configuration

[pavolloffay]

Jaeger OTEL components provide a default configuration - e.g. set of receivers, processors and exporters. These components have their own configuration that can be supplied via flags and/or config file.

Users should always know what components are being used and how are they configured. A possible solution is to print the configuration on the standard output. This could be done always at the startup or on-demand via a flag. To protect leaking of credentials it might be better to provide a flag that would print out the configuration just on demand.

[jan25]

Hi @pavolloffay , is this still a valid issue? I can try to fix

[pavolloffay]

It is a valid issue, if the default/hardcoded configuration is used, there should be a way to print out that config to the user. Users should know what configuration is used.

[pavolloffay]

Thinking how this should work, maybe the important parts of the config should be always printed at startup. We should also make sure that the auth config is never put into the logs.