Utkarsh Umesan Pillai

Thanks for that explanation @albertlockett! Even though it would be more performant to do this operation in the receiver, I don't think we should do it there. The receiver is...

@jmacd If you're following up with CNCF on this, could you please ask about "MPL-2.0" license as well? We did a [similar exercise](https://github.com/open-telemetry/opentelemetry-rust/pull/2936) for Rust SDK repo and found that...

`AnyValue` enum has bigger variants than `Value` enum. To test our hypothesis of enum size affecting the creation time, I did some benchmarking for the `enum` creation with varying sizes...

It looks like we already have a cancellable timer available here: https://github.com/open-telemetry/otel-arrow/blob/003401a21ff9c067cf135e137d475022ae4d61ff/rust/otap-dataflow/crates/engine/src/local/processor.rs#L206-L215 However, currently this has a limitation that there could only be one active timer for any given node....

> Other approach to explore: If the existing Rust Client SDK compatible with the requirements mentioned above, we could used it directly from the pipeline instances. OpenTelemetry Rust SDK for...

@yurishkuro > it seems we can do much better without introducing a whole new concept to the spec. The motivation for bounded instruments is to avoid a Hashmap lookup when...

Thank you! I look forward to helping maintain this repo.

@clhain Thanks for creating this issue! > Sending an encoded CEF format message directly without the syslog header fields does parse correctly, but as I read it, this seems like...

> Anyway, for now as long as we support syslog+cef that will help me. I have a demo running with CEF parsing in the go collector (using generic transform processors...

> Sadly not, as far as I know. The go collector is extremely rigid on compliance with either of the 2 rfc formats There is a [configuration](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/syslogreceiver#configuration:~:text=allow_skip_pri_header,be%20false.) in the Go...