Tyler Yahn

Results 600 comments of Tyler Yahn

This seems like standard Go behavior. The [`context` package explicitly states `nil` context should not be used](https://pkg.go.dev/context#Context): ![20240405_072833](https://github.com/open-telemetry/opentelemetry-go/assets/5543599/9fb68dbc-487a-40bb-9b0d-b035a7ffb219)

This seems like standard Go behavior. The [`context` package explicitly states `nil` context should not be used](https://pkg.go.dev/context#Context): ![20240405_072833](https://github.com/open-telemetry/opentelemetry-go/assets/5543599/9fb68dbc-487a-40bb-9b0d-b035a7ffb219) I do not think we should be adding boilerplate to all of...

User feedback requesting this feature: https://cloud-native.slack.com/archives/C01NPAXACKT/p1719249110767979

From SIG: - The STDOUT format is not a well thought out or agreed upon format. We do not want to standardize on this. - The OTLP is an agreed...

We cannot add support for this to `otel` until `log` is stable. If we want to support this prior to 1.0 a similar approach to https://pkg.go.dev/go.opentelemetry.io/otel/metric/global should be used.

I'm fine with a post-1.0. I think the metric one was motivated by a user ask and our desire to build a proof-of-concept for how it would work. I don't...

From SIG meeting: this looks almost complete. @dmathieu plans to another audit and review all coverage.

> @MrAlias, do you think it makes sense to add `MinSeverityProcessor` as an example? I was planning to [add it to contrib](https://github.com/open-telemetry/opentelemetry-go-contrib/pull/5817). That way it can be used by users...

@MadVikingGod as a codeowner, please take a look at this.