How to trace on goggle adk artifact using openinference-google-adk

[ruqianq]

Hi community,
I use auto-instrumentation from openinference and from phoenix UI I dont see the artifact is being traced on? do I need to manually trace on artifact, what attributes would you recommend me to use? Thanks!

for reference: https://google.github.io/adk-docs/artifacts/

[dosubot[bot]]

Auto-instrumentation with openinference-google-adk currently does not fully trace Google ADK artifacts created from bytes (like images or PDFs). This is a known limitation: the instrumentation only extracts text fields from google.genai.types.Part objects and logs an error when it encounters inline_data or file_data parts, which are common for artifacts. As a result, these artifacts may not appear in Phoenix UI traces, even though API calls succeed details.

To trace artifact operations (such as save_artifact, load_artifact, or list_artifacts), you’ll need to add manual instrumentation. You can do this by wrapping these methods with a tracer and setting relevant span attributes. Recommended attributes for artifact tracing include: filename, MIME type, data size, operation type (e.g., save/load/list), and status. Use OpenInference semantic conventions like input.value, input.mime_type, output.value, output.mime_type, and add custom attributes for artifact-specific metadata semantic conventions.

Here’s a quick example for manual tracing:

from phoenix.trace import tracer

with tracer.start_as_current_span("save_artifact") as span:
    span.set_attribute("artifact.filename", filename)
    span.set_attribute("artifact.mime_type", mime_type)
    span.set_attribute("artifact.data_size", len(data))
    # ... perform save_artifact logic ...
    span.set_status(Status(StatusCode.OK))

If you want to work around the current instrumentation limitation for image/PDF parts, you can monkey-patch the _get_attributes_from_part method to extract and log mime_type and data size for inline_data or file URI for file_data workaround code.

For best results, run your agent in a fresh environment, initialize the instrumentor only once, and use a ConsoleSpanExporter to debug raw trace payloads before they reach the UI setup tips.

Let me know if you need a more detailed code template for manual instrumentation!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[axiomofjoy]

Hey @ruqianq, I'm not deeply familiar with Google ADK. Can you take a look the linked issue to see if it describes the issue you are facing?

[ruqianq]

probably, guess behind the theme it was able to log the artifact, in my case it is a pdf file.

[axiomofjoy]

Filed an issue here. Thanks for reporting!