Replies: 2 comments
-
|
@dwelias even though the spans are marked as read-only you should be able to modify them in the span processors or exporters. Hope that helps. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Unf the span is readonly, I was able to make a copy of the span but it wasn’t complete so it broke the trace relationships. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am looking to encrypt certain attribute values in the spans going out to Phoenix. I don’t have the ability to run a collector so am trying to do it on the client side.
So far I have created a filter span per the [https://arize.com/docs/phoenix/tracing/how-to-tracing/advanced/modifying-spans ]documentation. I then encrypted the attributes I needed but cannot update the span as it’s a readonly so I created a new span using tracer.start_span which seemed to work but it broke the trace as each span now shows up as a separate trace.
Should I be using tracer.start_as_current_span?
Is this the right approach or are there any other options?
Beta Was this translation helpful? Give feedback.
All reactions