David Ashpole

https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33223

I would recommend using scrape metrics to debug this, such as `up`, and `scrape_series_added`. That should help you tell whether or not prometheus was able to scrape the endpoint, and...

Sorry, it looks like you are not using the OTLP receiver in your collector configuration. Do something like: ```yaml receivers: otlp: protocols: grpc: endpoint: x.x.x.x:4317 http: endpoint: x.x.x.x:4318 exporters: logging:...

@fatima-Zahra95 I would recommend opening a new issue. This one was a misconfiguration.

> Can this doc be made publicly accessible? I don't believe it can be. Feel free to request access.

> But as mentioned by others, the document you linked hasn't been made public yet. It might also make sense to allow some time for discussing the contents of the...

@reyang anything else needed for this to merge?

Also, should we document the convention that the go import path of the library producing the telemetry should be used as the scope name?

> @dashpole do you think this is adequate documentation? yes, thank you!

I think this is WAI. If we added the callback, it would result in a memory leak over time. We explicitly document this in the SDK readme: https://pkg.go.dev/go.opentelemetry.io/otel/sdk/metric#pkg-overview. The correct...