Reiley Yang
Reiley Yang
Refer to https://github.com/open-telemetry/opentelemetry-python/tree/v1.10.0/shim/opentelemetry-opentracing-shim.
Implement W3C TraceContext and get 100% pass rate from the validation service https://github.com/w3c/trace-context/tree/master/test. CI should be implemented which verifies the TraceContext compliance.
Currently the screenshots look bad under dark theme 
# Bug Report List of [NuGet packages](https://www.nuget.org/profiles/OpenTelemetry) and version that you are using (e.g. `OpenTelemetry 0.4.0-beta.2`): * 1.0.1 Runtime version (e.g. `net461`, `net48`, `netcoreapp2.1`, `netcoreapp3.1`, etc. You can find this...
https://github.com/open-telemetry/opentelemetry-dotnet/runs/6511353944?check_suite_focus=true ```text [xUnit.net 00:00:00.81] OpenTelemetry.Exporter.Prometheus.Tests.PrometheusExporterHttpServerTests.PrometheusExporterHttpServerIntegration [FAIL] [xUnit.net 00:00:00.81] System.Net.Http.HttpRequestException : Connection refused (localhost:4983) [xUnit.net 00:00:00.81] ---- System.Net.Sockets.SocketException : Connection refused [xUnit.net 00:00:00.81] Stack Trace: [xUnit.net 00:00:00.82] at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32...
Before we release the Stable version of the instrumentation libraries, we need to elaborate the exact meaning of an Activity duration. Here goes an example that we might want to...
https://github.com/open-telemetry/opentelemetry-dotnet/runs/6341673991?check_suite_focus=true ```text warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35] No XML encryptor configured. Key {ac735029-a892-49f8-b14e-27dfa0215199} may be persisted to storage in unencrypted form. fail: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[1] An unhandled exception has occurred while executing the request. System.Exception:...
Python started to support async/await syntax in version 3.7. We want to explore how to support this in OpenTelemetry Python. Things to be explored are: 1. Do we provide this...
We don't yet have a guideline regarding how language SIGs should sign the binaries that they release. We're seeing asks from multiple SIGs: * https://github.com/open-telemetry/opentelemetry-dotnet/issues/1302 * https://github.com/open-telemetry/opentelemetry-collector/issues/5254 A possible solution...
This is to follow up the non-blocking comment https://github.com/open-telemetry/opentelemetry-specification/pull/2404#discussion_r828331793. Discussed during the 3/18/2022 triage meeting, we consider this as a nice wording change which doesn't block #2404.