Tyler Helmuth

With https://github.com/open-telemetry/opentelemetry-collector/pull/10413 merged, I am removing this from the component 1.0 milestone and Collector V1 project.

@evan-bradley ready for another review

I don't believe there was any blocking reason. We still want this, but it has been hard to prioritize.

I love the idea of moving forward with this work. According to the [collector end-user survey](https://opentelemetry.io/blog/2024/otel-collector-survey/) k8s and the collector are a big part of our end-user's stack, so moving...

@dmitryax might know

> our default redaction list only includes known query string keys used to pass credentials to known public rest APIs I agree with adding this verbiage as it helps clarify...

@lmolkova the PR went with attributes because that has been the standard for collector translators/components so far. I believe the `k8sobjectsreceiver` is an early implementor of the event concept, but...

Another question: My understanding is that for any `event.name` value, the payload (log body in this case) should always be same. Do we have that guarantee with the data being...

> we're missing: central SDK/collector component that'd do scrubbing to comply with GDPR and or other requirements relevant to a certain application To my knowledge this is not true, the...

My understanding of query parameters is that, while they can be abused to leak sensitive information, that is considered a mistake. Is there anything in the w3c that defines query...