Phillip Carter

Works for me.

Assigning myself here. The package does work, I just need to fit it in correctly with a good code sample.

Blegh. Unfortunately stumped because it's to do with environments and there's wonky behavior: * `service.instance.id` always shows up even though it's not in `env` * The package doesn't appear to...

Aha, this explains the `service.instance.id` being set: https://github.com/open-telemetry/opentelemetry-dotnet/blob/d7afc1bcb0092a56ac1ea55bfbcf5a9430c72cf9/src/OpenTelemetry/Resources/ResourceBuilderExtensions.cs#L54

(follow python example for each language: https://opentelemetry.io/docs/instrumentation/python/getting-started/) # Getting started words ## Installation install everything you need / set up an environment for it if the language calls for it...

(In existing manual instrumentation article) # Manual instrumentation words ## Tracing ...all the tracing stuff that's mostly documented now ## Metrics words ### Initialization ✨✨ **HELP NEEDED!** ✨✨ Show how...

Hmm. While potentially helpful (both this and the status page get similar request counts as per https://play.honeycomb.io/opentelemetry-web/datasets/opentelemetry.io/result/ba7ffkzuZB7?useStackedGraphs), I think this should link to each page's status anchor instead. We followed...

Hey, sorry for no reply here. I think for now, it'd be best to just replace each entry in the table with a link to the anchor for each status...

@kainawroth with https://github.com/open-telemetry/opentelemetry.io/blob/main/data/instrumentation.yaml this can now be more data-driven. How would you feel about updating the table to pull in data from here, similar to https://github.com/open-telemetry/opentelemetry.io/pull/1732?

Just a nit about .NET - it's explicitly not an agent (@pellared can confirm) but rather a custom profiler & assorted components that injects the instrumentation. So we'd want to...