Currently it is pretty hard to communicate a configuration error encountered when ELAPI initializes to the caller. We are limited to the error code (and message) but it is hard to communicate which target or sink the problem is related to.

I was envisioning that the dispatcher can internally be built to contain some verbose information that will report the processing of the config file, loading sink providers and initializing them. Then there will be a very simple utility that will:
1. Link with verbose version of the dispatcher
2. Take a config file and application name as arguments
3. Create validation dispatcher
4. Load all targets, sinks and providers.
5. Initialize all sinks and make sure that they can connect to their data storages.