Robert Pająk

>> it only finds a "substring" > You can also use the project field, like https://issues.oss-fuzz.com/issues?q=customfield1349507:opentelemetry It works the same way. Notice bugs for `opentelemetry-go-contrib` project if you follow the...

> I think you can just submit a pull request with an improvement. Should all hyperlinks like `https://bugs.chromium.org/p/oss-fuzz/issues/` be updated to `https://issues.oss-fuzz.com/issues`?

@zhihali, this is for all OTLP exporters. I see that OTLP trace and metric exporters are already fixed. Therefore, only OTLP log exporters need bugfixes.

@mx-psi @jpkrohling Is this issue still valid? Personally, I have not encountered it for several months.

@zhihali, are you still working in it?

@klauspost, this needs to be a proposal in https://github.com/open-telemetry/opentelemetry-specification Check if there are other similar issues, because I think the issue you are trying to solve is quite common. Here...

> Is the expectation that filtering is done at the OpenTelemetry level based on severity? (From my experience, such filtering is typically done inside the logging framework itself, so logs...

@bogdandrutu, what I described was just a clarification that allowing filtering by severity is needed also for logging library bridges (at least in Go). I think that nothing I wrote...

FYI @dmathieu, @dashpole

> I suggest the SDK should always escape until we have update the spec to allow for the proper no-translation mode Can you please give more context as personally I...