Marc Pichler

> There could be couple reasons for these new dependencies. What is the most likely reason here? And as a developer how is one supposed to know that these are...

Hi @bozzelliandrea, thanks for reaching out. This looks like it's actually `@opentelemetry/sdk-node` loading `@opentelemetry/exporter-logs-otlp-grpc`, not the `@opentelemetry/exporter-logs-otlp-http` loading the `@grpc/grpc-js` module. Would you mind importing `SimpleSpanProcessor` from `@opentelemetry/sdk-logs` instead? (as...

A side node: if you're planning to use this in production, I'd highly recommend using a `BatchLogRecordProcessor` instead. A `SimpleLogRecordProcessor` will essentially make one request per log, which will introduce...

> Hi @pichlermarc , thanks for the fast reply 😄, the SimpleLogRecordProcessor from `@opentelemetry/sdk-logs` seems not working btw. It compile and run, but it won't process the logs. Is there...

@bozzelliandrea - I've tried to reproduce this locally but I'm having a lot of trouble setting up a system where I run into the same issues that you run into....

@KirilSoshnin yes, that's a feature request - #4631 asks for a trace otlp fetch exporter but the same steps are needed for a logs exporter too, they share the same...

Hi @dormesica, thank you for your PR. Due to organization policy, we unfortunately cannot accept PRs unless the CLA signed. Please see [here](https://github.com/open-telemetry/opentelemetry-js-contrib/pull/2710#issuecomment-2653442663) for information on how to sign it....

Categorized as P4 (logspam) - looks like there's no need to log an error in this case. cc @jj22ee (component owner) (side note: It's a bit of a weird feature...

Closing this as this was addressed by #2753

I'll assign @Victorsesan as they were first.