-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[processor/transform] Unable to rename operation field #11859
Comments
cc @TylerHelmuth maybe you can help? |
@klubi the All that said, the way you have configured the processor you should at least be getting values modified to |
This is exactly what I'm looking for. I'm on latest versions of collector and jaeger. I can setup docker-compose example over weekend to demonstrate the issue. But i guess my question boils down to: "how to reference and alter field used by jaeger to display operation name". |
I'm not familiar with jaeger so I won't be much help with the data once it is there. For debugging the collector, though, enabling a logging exporter with logLevel set to Debug is a very useful way to inspect the data that would get exported to a backend. With the configuration you posted, assuming the transform processor is also added to the traces pipeline, I would expect it to be modifying all those attributes, assuming that all match the pattern. |
Ok... after enabling debugging it looks like, what I'm looking for is changing span name (see span #1)
|
Yes, you can do transform:
traces:
queries:
- replace_match(name, "*.domain.com", "{subdomain}.domain.com") |
Perfect!! That worked like a charm! |
Hi
I'm having an issue renaming operation field.
My simplified environment setup:
API Gateway sends data in Zipkin format.
In my setup, there are plenty of subdomains and I'd like operation related field to be more generic, so in jaeger they won't be listed as separate operations, but rather be grouped.
I tried using
transform
processor, but wasn't able to make it work...The text was updated successfully, but these errors were encountered: