Edmo Vamerlatti Costa

Hi there! may I get this issue assigned? I'm working on a lib for doing exactly this and could be submitting a PR soon.

@michalpristas @TylerHelmuth, I think we should close this issue as it was done by https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/34353. Thanks!

Hi @DanSheps! Thank you for reporting! I'm not sure if I fully understood this issue, could you please provide more context on the expected behaviour and the used pipeline's `split`...

Duplicate of https://github.com/logstash-plugins/logstash-integration-snmp/issues/30

> We'll want to update the hash function alternative recommendation, but otherwise this looks good to me. Thanks @edmocosta. Thanks for reviewing folks! I've applied @evan-bradley suggestion to update the...

Hi @MovieStoreGuy! I completely agree with you regarding using a more secure/non-colliding hashing algorithm, especially for encryption. But MD5 was widely used for fingerprinting/checksum files for example, and forcing users...

Hi @evan-bradley! Thanks for chime in! Here's my two cents: > I think the one difference between MD5 and SHA1 here is that SHA1 hashes are supported by the attributes...

Hey folks, any thoughts on this? It seems it was identified as missing feature [here](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31930).

Thanks folks for considering this feature! I did submit a [PR](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33793) a time ago, if everyone agrees on that, I think we could re-open it!

> Sounds good, I've reopened the PR. Could you make any necessary updates and we can start the review process? It seems the PR code is still valid, I've updated...