You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We keep track of the generate trace id but we can't map the generate trace id back to the session.
The trace should probably have a session id corresponding to its session
gcloud logging read "logName=\"projects/foyle-dev/logs/foyle\" AND jsonPayload.message=\"Agent.Generate\" AND jsonPayload.traceId=\"0233d9db2c290bbccca0e1d14dc0d9c7\"" --freshness=7d
Use that to get the streamTraceId
You can then query for the logs using the streamTraceId.
gcloud logging read "logName=\"projects/foyle-dev/logs/foyle\" AND jsonPayload.message=\"Received full context\" AND jsonPayload.traceId=\"a5389130309ce9f7d9be9f3a6be9da0d\"" --freshness=7d
I don't think we have a great way right now to map a block back to its session.
Here's the BlockLog proto
foyle/protos/foyle/logs/blocks.proto
Line 14 in b8ee786
We keep track of the generate trace id but we can't map the generate trace id back to the session.
The trace should probably have a session id corresponding to its session
foyle/protos/foyle/logs/traces.proto
Line 19 in b8ee786
I think a work around is to query the logs.
The text was updated successfully, but these errors were encountered: