Add NewExportPipeline and InstallNewPipeline functions to OTLP exporter

[MrAlias]

Similar to the other exporters:

• opentelemetry-go/exporters/metric/prometheus/prometheus.go

  Line 90 in 3d6e8b5

  func NewExportPipeline(config Config, options ...pull.Option) (*Exporter, error) {

• opentelemetry-go/exporters/stdout/exporter.go

  Line 53 in fd3c82b

  func NewExportPipeline(exportOpts []Option, pushOpts []push.Option) (trace.TracerProvider, *push.Controller, error) {

• opentelemetry-go/exporters/trace/jaeger/jaeger.go

  Line 154 in fd3c82b

  func NewExportPipeline(endpointOption EndpointOption, opts ...Option) (trace.TracerProvider, func(), error) {

• opentelemetry-go/exporters/trace/zipkin/zipkin.go

  Line 114 in fd3c82b

  func NewExportPipeline(collectorURL, serviceName string, opts ...Option) (*sdktrace.TracerProvider, error) {

add the NewExportPipeline and InstallNewPipeline convince functions.

[binjip978]

Hello, i would to help with this issue, looks like open-telemetry/opentelemetry-collector#2159 can be taken as reasonable defaults.

[MrAlias]

@binjip978 sorry about the late response, thanks for picking this issue up. I think there might be some differences between what the other exporters do and what that example does. We should try to remain consistent with what the other examples do.

[eggyhead]

👋 looking through the linked code and wanting to understand the intention of this change since all the examples are slightly different. @MrAlias could you possibly summarize the behavior of these methods for oltp?

[MrAlias]

This issue is outdated at this point. Closing.