Replies: 3 comments 5 replies
-
|
I was going to create a similar issue as well. I think this will be very important for the 99% use case. Tracing today is really meant to trace the core runtime, but most users don’t care about that, they only care about the interactions they control. |
Beta Was this translation helpful? Give feedback.
5 replies
-
|
@ekzhu any comments? if there is a way to suppress these event messages? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I agree we should separate tracing from the runtime, and tracing of agent chat agents. I will create issues for these |
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.
-
@ekzhu @victordibia I posted this question on other discussion thread but thought maybe it's better to ask here. I am trying to find a way to disable runtime messaging events. I want to customise my instrumentation and want to capture mostly the span attributes related to llm calls and tools but with the runtime event the whole hierarchy just gets spammed with too much information.
Beta Was this translation helpful? Give feedback.
All reactions