Paulo Janotti

The failure below is due to it missing the expected string, but, in this case it seems related to be missing the expected metric https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/runs/7648224878?check_suite_focus=true#step:4:3005

There seems to be a synchronization problem with the test in this failure here https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/runs/7639823504?check_suite_focus=true#step:4:3004 https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/runs/7639820988?check_suite_focus=true#step:4:3005 It seems to get its answer after the first reply from the server, but...

OTLP protocol is also related to this issue, see https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/pull/708/files#r886378692

@dszmigielski I found just one such case, see #1082.

> OTLP protocol is also related to this issue, see https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/pull/708/files#r886378692 Separating OTLP settings per signal is a much bigger issue, let's track it at #1083

@piyushbicycle fyi we just switched the main branch on the repo so now we are using the previously named `poc-otel-sdk`, so a lot of changes. Anyway, this error happens when...

Yes, that is correct - but initial goal is to have some manual suite to track performance impact.

Instead of having these individual rules coming from each automatically detected PNSE it seems that it will be better to move the platform compatibility rules (PC) to a format similar...

Hi @springy76 - yes you are correct, the tool is lacking context information in this case: since it depends on the value of a parameter passed to the methods.

Hi @rcosnita - new exporters should be created at the OpenTelemetry Collector Contrib repo. See https://github.com/open-telemetry/opentelemetry-collector-contrib#opentelemetry-collector-contrib for some info. Would you like to contribute to it? Per your description, you...