[Page feedback]: Add examples and best practices to Go exporters documentation

[jcranfordbeyondtrust]

URL

https://opentelemetry.io/docs/languages/go/exporters/

Description

Need examples of how to separately create and return:

1. *metric.MeterProvider
2. *trace.TracerProvider
3. *log.LoggerProvider

Include best practices such as

1. Batching
2. Vender neutrality (e.g. metricsProvider should have pull provider Prometheus for local testing, and push provider for preprod testing)

[tiffany76]

@open-telemetry/go-approvers, PTAL. Thanks.

[pellared]

Need examples of how to separately create and return:

1. *metric.MeterProvider
2. *trace.TracerProvider
3. *log.LoggerProvider

This is in https://opentelemetry.io/docs/languages/go/instrumentation.

Include best practices such as

1. Batching

This is also included in https://opentelemetry.io/docs/languages/go/instrumentation. Notice also that examples in https://pkg.go.dev (for instance https://pkg.go.dev/go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp#example-package) do that. Maybe we should remove the code snippets from https://opentelemetry.io/docs/languages/go/exporters ?

2. Vender neutrality (e.g. metricsProvider should have pull provider Prometheus for local testing, and push provider for preprod testing)

ad. 2
Is there anything not vendor-neutral in our docs? The suggestions you provided are subjective. Some may prefer to use logging exporters or use OTel Collector for local testing. Using Prometheus for production is also fine.

@open-telemetry/docs-approvers, can you follow-up please?