Trevor L.

Deploying Phoenix for GenAI: A Complete Guide with Docker/Kubernetes

For those working on GenAI applications, it's critical to have a tool at your disposal that can help with all phases of the development cycle (i.e., early development, testing/staging, production) that's easy to get started with / run locally, and deploy within your infrastructure if needed. Phoenix can give you just that! Check out the tutorial below on how to deploy Phoenix via Docker/Kubernetes and the different data persistence options you have available. https://youtu.be/9hNrosMqirQ

0Comments

Commented on Clarification on Using suppress_tracing Context Ma...·Posted inPhoenix Support

Trevor L.

as they have "native" instrumentation

This refers to the package creating spans with this tracer.start_as_current_span(name) as cur_span: , right?

Commented on Clarification on Using suppress_tracing Context Ma...·Posted inPhoenix Support

Trevor L.

Thanks Mikyo! Just to confirm, there's 2 things we can try:

1.
We could try adding the snowpark package to the OTEL_PYTHON_DISABLED_INSTRUMENTATIONS env variable to see if that disables it
2.
We could patch snowpark and add the ability to disable the creation of spans in the above file even if the otel package is found

Commented on Clarification on Using suppress_tracing Context Ma...·Posted inPhoenix Support

Trevor L.

We're also testing setting the TRACE_LEVEL to OFF to see if that resolves

Commented on Clarification on Using suppress_tracing Context Ma...·Posted inPhoenix Support

Trevor L.

Yeah we tried setting that to False but the spans were still showing up in the console. It looked like that parameter just disables them from showing up in Snowflake

Commented on Clarification on Using suppress_tracing Context Ma...·Posted inPhoenix Support

Trevor L.

When using the to_pandas() method, it looks like that's where the spans are being created. I'm still trying to figure out how to turn it off though

Commented on Clarification on Using suppress_tracing Context Ma...·Posted inPhoenix Support

Trevor L.

Yeah I'm reading through some of the Snowflake docs because I think it's coming from there. Not too familiar w/ Snowpark but trying to see how to suppress tracing directly there instead

Commented on Clarification on Using suppress_tracing Context Ma...·Posted inPhoenix Support

Trevor L.

Thanks for the response Mikyo! We aren't creating any spans manually which is why I was a bit confused still. Does the above code check if the suppress instrumentation key is set on the current context?

Posted in Phoenix Support·

Trevor L.

Clarification on Using suppress_tracing Context Manager in OpenInference

Quick clarification question on the suppress_tracing context manager. Could we use that to wrap any function we don't want spans to be captured for (e.g., even with spans that are generated outside of an openinference autoinstrumentor)? There are a few calls to get data from Snowflake tables (using snowpark) that happen in the application, and spans for those function calls are still showing up in the console and Phoenix even when wrapping the functions with suppress_tracing , so not sure if it's being used correctly.

16Comments

Commented on Support for Google Gemini-Vision in Phoenix/Evals?·Posted inPhoenix Support

Trevor L.

Hey Ilya! Is this for the same use case we worked on together a while back?