Tyler Helmuth

> For this particular use case we could instead update replace_all_patterns to take a new parameter (string or enum) that specifies whether the function applies to keys or values and...

I believe this PR duplicates functionality that already exists in the transformprocessor. I'm not saying thats unacceptable necessarily, but this is possible to do in the collector today.

@open-telemetry/collector-contrib-approvers how do we want to handle duplicate functionality? @boostchicken would users always need a unique instance of the spanprocessor thats dedicated to changing span.kind or could it be added...

Does this issue cover your needs: https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/10358

If the workflow is doing nothing then I support disabling it.

Instead of changing key names you should be able to use the "set" function to create a new attribute with the existing attribute and then use the "delete" function to...

Oh but I see that you want to change potentially all the keys, not specific ones. Ya I don't think we support that yet.

> Regex named capture groups don't allow for . characters in the capture group and I want my attribute keys to follow the Otel naming standard of using .s. Are...

If it is only those three you could do ```yaml transform/key_rename: traces: queries: - set(attributes["prefix.http.protocol"], attributes["prefix_http_protocol"]) - set(attributes["prefix.http.domain"], attributes["prefix_http_domain"]) - set(attributes["prefix.http.path"], attributes["prefix_http_path"]) - delete_matching_keys(attributes, "^prefix_+") ``` But I agree that...

Yes a new function could do it. It would be very similar to `replace_all_patterns`.