Adding a custom SpanProcessor means giving up on env-var based defaults?

[richardszalay]

I'm looking to add a custom SpanProcessor as I want to enrich some attributes, but as far as I can tell this would result in me having to replicate all of the functionality in getSpanProcessorsFromEnv and getOtlpExporterFromEnv myself. Is that correct and/or intentional?

It seems that NodeSDK.start won't call getSpanProcessorsFromEnv if any spanProcessors were provided, and since getSpanProcessorsFromEnv / getOtlpExporterFromEnv aren't exported by the SDK there's no way to call them myself.