24 Feb 2025
01:43 PM
- last edited on
10 Mar 2025
07:41 AM
by
MaciejNeumann
I have a service that uses that same URL for every request, even though every request is not doing the same thing. The good news is that we have been able to apply Otel instrumentation to the service and can see a span in our traces that tells us more specifically what the request is. The bad news is that you can only really see this data within a single trace. I would like to use the Otel attribute value as the service request name, can this be done?
Solved! Go to Solution.
07 Mar 2025 09:18 PM
It looks like there are some hard limits currently around endpoint naming for unified services. Fingers crossed that OpenPipeline will soon gain the ability to modify span data on arrival. Perhaps post this type of functionality as a product idea..