Anatoly S.

Commented on Seeking Help with OpenInference Instrumentation in...·Posted inPhoenix Support

I see. Thank you very much! I think I will take this approach. In addition, it would solve the issue I mentioned in another thread. 👍

Commented on Seeking Help with OpenInference Instrumentation in...·Posted inPhoenix Support

Anatoly S.

I did try that; but, it means that in Phoenix UI, in the spans list, I will see empty inputs and outputs, and I will need to click on each and then drill to the span created by the instrumentation. I thought maybe I could avoid that and instead attach the attributes to the span that the instrumentation creates.

Posted in Phoenix Support·

Anatoly S.

Improving Trace Display: JSON to Human-Friendly Format

Another question: we instrument our app with openinference-instrumentation-bedrock = 0.1.13, and Phoenix is 7.8.1. The instrumentation successfully submits the traces. But, on the traces page, the input and output columns show JSON pieces instead of plain text. See the screenshot. On the second screenshot, you can see that the individual screen for this trace shows the output in a human friendly way. Maybe we could tweak some options to get the main screen show us nice view of the messages as well? Thanks!

3Comments

Commented on Seeking Help with OpenInference Instrumentation in...·Posted inPhoenix Support

Anatoly S.

Let me know if I can provide more relevant information. Thank you!

Commented on Seeking Help with OpenInference Instrumentation in...·Posted inPhoenix Support

Anatoly S.

I tried placing the line

current_span = trace.get_current_span()

in different places in this code snippet, to no avail.

Commented on Seeking Help with OpenInference Instrumentation in...·Posted inPhoenix Support

Anatoly S.

Here, retrieve_reply_for_chat() is the iterator which contacts AWS Bedrock. This code does post a span to Phoenix — but the custom attributes are not there.

Posted in Phoenix Support·

Anatoly S.

Seeking Help with OpenInference Instrumentation in Bedrock

Hi Phoenix team, thanks for the great product! I am writing to expand on the thread by my colleague David above. We're using openinference-instrumentation-bedrock = "^0.1.13" to instrument a stream-oriented interaction with Bedrock but we do not seem to be able to submit custom attributes to the span that's being created. Maybe you could point to where I am doing it wrong? Will elaborate in the thread🧵

10Comments