Instrumentation for Gemini via Google GenAIClient library #14
Conversation
realark
changed the title
realark
force-pushed
the
ark/gemini-instrumentation
branch
6 times, most recently
from
eed887d to
53685c4
Compare
realark
force-pushed
the
ark/gemini-instrumentation
branch
from
53685c4 to
2bf5b19
Compare
| var requestJson = JSON_MAPPER.readValue(requestBody, Map.class); | ||
|
|
||
| // Extract metadata fields | ||
| for (String field : |
There was a problem hiding this comment.
my recommendation is to pass the literal input and output to the span. at rest it'll look liek
(ref)
you may find that the ui will automatically render java produced spans automatically
There was a problem hiding this comment.
Yeah I agree, I'd much rather do that (or even better just send the entire request/response body and let the backend sort it out)
I think we need to update the backend to support otel here? I tried just sending the input contents directly on both braintrust.input and braintrust.input_json but the BE doesn't recognize that as an LLM message (I just get raw json/yaml views)
| } | ||
|
|
||
| span.setAttribute( | ||
| "braintrust.input_json", JSON_MAPPER.writeValueAsString(inputJson)); |
There was a problem hiding this comment.
i know that it'll be a little different since we're using otel ingestion, but it should be the same thing if we just make sure the input is literal input and so on.
realark
force-pushed
the
ark/gemini-instrumentation
branch
from
2bf5b19 to
4312cd2
Compare
|
Talked offline: plan is to update the backend to support parsing gemini messages. Once that is in place I'll update this instrumentation to use that simpler approach, but in the meantime I'm going to merge this in to get gemini support into the SDK. |
No description provided.