-
Notifications
You must be signed in to change notification settings - Fork 533
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Watsonx Orchestrate Logs issue #1229
Comments
Is there any way you would be able to show me the log entry you are receiving that is not being parsed correctly? With it, I would be able to compare that entry with what the java sdk is expecting |
@apaparazzi0329 Sure, response from `/logs?version=2024-08-25&filter=response.context.global.system.user_id::608c87d3-17c6-423d-b0b5-cf97987a6900,request.input.text::!""&pageLimit=400&sort=-request_timestamp |
Comment from IBM support: It's because Assistant API returns the extra fields (properties) which are not defined inside the SDK https://github.com/watson-developer-cloud/java-sdk/blob/master/assistant/src/main/java/com/ibm/watson/assistant/v2/model/ Generally, there are three ways to resolve: Assistant API: not to return non-defined fields |
Hi, @apaparazzi0329 Any updates? |
I am discussing with the team now on what should be done here |
@Vitals9367 Are these logs from the v1 or v2 endpoint? |
@apaparazzi0329 Logs are from v2. |
com.ibm.watsonOverview
We are fetching logs from WxO assistant and this is an error that some people are getting. It's inconsistent. Seems like it fails to parse log response from assistant.
We are wondering if this is a SDK issue or product returns invalid logs.
How to reproduce
Help us to reproduce what you experienced. Include your code snippets (without credentials)
It's breaking and this return line.
SDK Version
The text was updated successfully, but these errors were encountered: