Phillip Carter

Another one: https://cloud-native.slack.com/archives/CJFCJHG4Q/p1643212043135500?thread_ts=1643187503.132000&cid=CJFCJHG4Q This is for span status: "Don't set OK unless you're overriding ERROR"

@iomari could you specify your steps to reproduce this behavior? Specifically, steps run to create the app in the first place (packages installed, etc.) and sharable code if possible.

Hmm, seems like something unrelated to this change is borking CI?

At this point it's quite diverged from the existing getting started, and it also follows a different format. I think that since .NET supports all three signals today, it's good...

I will close this due to inactivity + divergence from the docs. But I'm more than happy to look at another go at this, so feel free to ping here...

I think it is fine to keep it as-is for now. These are about deployment models/strategies. I think we can extend the page over time to have specific guides, but...

What sort of content would you expect to be here, showing how to use B3 propagation instead of W3C? I mainly ask because in Go, context propagation isn't on by...

In this case of JS (and most languages), context propagation is one by default ([source](https://github.com/open-telemetry/opentelemetry-js/blob/main/packages/opentelemetry-sdk-trace-base/src/BasicTracerProvider.ts#L55-L62)) and it's set to W3C because that's the default format chosen for OpenTelemetry. You may...

When you instrument either via exclusively automatic instrumentation, or you manually use one of `BasicTracerProvider`/`NodeTracerProvider`/`WebTracerProvider` then context propagation will be on by default (Node and Web both subclass `BasicTracerProvider`). These...

Gotcha, sorry, I think I misunderstood your questions here. Yes, if you don't have instrumentation for calls across service boundaries, then context cannot propagate across those boundaries automatically. Your only...