Tyler Yahn

Hey @austinlparker thanks for getting the GCP project setup. Can you add me ([email protected]) to the project as well.

It looks like the lint CI is failing. Please run `make precommit`, it should fix the issue.

The logging bridge is not meant to provide the scope name. It is a bridge, not instrumentation. The instrumentation that uses the logging library backed by a bridge needs to...

> The provided name needs to uniquely identify the code being logged. This is most commonly the package name of the code. https://pkg.go.dev/go.opentelemetry.io/contrib/bridges/otelslog#NewHandler The specifics are going to depend on...

> Even if the processor would to accept a fully mutable record - this processor would still be helpful. However, we can postpone this if this is your preference, then...

I do not think we should accept this change. It adds an exporter that has not been stabilized at the specification level. This addition will add churn to our stabilization...

This looks like it needs to be transferred to https://github.com/open-telemetry/opentelemetry.io

The uptime metric was deprecated in https://github.com/open-telemetry/opentelemetry-go-contrib/releases/tag/v1.29.0. Closing.

@huiyifyj can you please provide justification for your previous assertion.

For Go it is `Detector.Detect`: https://pkg.go.dev/go.opentelemetry.io/otel/sdk/resource#Detector