Cardano.Logging.Configuration

Call this function at initialisation, and later for reconfiguration. Config reflection is used to optimise the tracers and has to collect information about the tracers. Although it is possible to give more then one tracer of the same time, it is not a common case to do this.

Take a selector function called extract. Take a function from trace to trace with this config dependent value. In this way construct a trace transformer with a config value

Filter a trace by severity and take the filter value from the config

Set detail level of a trace from the config

Routing and formatting of a trace from the config

Routing and formatting of a trace from the config

Switch off any message of a particular tracer based on the configuration. If the top tracer is silent and no subtracer is not silent, then switch it off

By guaranteeing fallback values in the config's namespace root, the Debug severity value here should never get used. If it has to be used, this points to a severely erroneous config, or an implementation error in the application's MetaTrace instance(s). For those cases only, this ensures the affected trace message isn't silently filtered out.

If no details can be found in the config, it is set to DNormal

If no backends can be found in the config, it is set to [EKGBackend, Forwarder, Stdout HumanFormatColoured]