Steve Gordon

@lmolkova Over on the runtime issue, I have the go-ahead to implement the metrics inside the runtime itself. This will likely be a port of the existing metrics from the...

I think it's reasonable to implement the metrics in the runtime to align with the conventions established for Java. Consumers can opt into those from the runtime or stick with...

@lmolkova Starting with these as experimental makes sense. I'm hoping to also contribute to the implementation in runtime so we can move to stable once those are merged and we...

@martinjt, this is another issue I think we can close. Things have moved on since this was opened. For inbound HTTP requests, query string parameters are now redacted by default...

@martinjt This one looks to have been resolved in #3266 so I think it can be closed.

I'd be interested in helping with .NET too, if needed.

@JamesNK I'm still getting up to speed in this repo, so I'm adding some notes that may or may not be obvious to anyone finding this issue. I was also...

Yes, the fact that gRPC doesn't use `OtlpExporterOptions. ' HttpClientFactory` is a pain, and I ran into that with something else, too. From a quick scan of the code, it...

@sarchibald-mdsol Are you including a header `My-Custom-Correlation-Id` in your request? With `EnforceHeader=true`, this is the expected behaviour if incoming requests do not include the header. I cannot reproduce an issue...

run docs-build