Closed jack-berg closed 1 year ago
Any thoughts on what the validation story looks like for jaeger since some of the options only apply to specific protocols? i guess it would be no different than different options per type of exporter?
This is another example where its likely that the validation falls on the logic that's interpreting the config, rather than in the schema itself. Another example is that span and log processors reference names of exporters which are separately configured. JSON schema allows conditionals where certain bits of schema are only enforced when certain criteria is met, but other schema technologies will likely struggle with this. If we eventually choose JSON schema there's the question of whether we should express things like this even if it has the tools to do it.
Completes a couple of TODOs.