Log intents not recognized with WA

Hi @agorostidi it is something that should be integrated to the new version of Watson Assistant, that with a simple integration through a script can generate an external DB and be able to visualize the statistics and conversations. This would expedite the provision of these data to customers. But obviously there is no IBM or another team who knows how to do it or there is no possibility.

@estebanp, please clarify your remarks. On the one hand, you seem to say that a new version will include exactly what is requested, but on the other hand you say there is no possibility of something. Also, are you talking about the plugin or about the back end?

@josiah-s-carberry my apologies, maybe i was not clear. I say: In the current version “2” of the Watson Assistant API should have an integration that allows exposing the logs of the conversations through a UI to the end users. Currently the logs are only available in the “Improvements” section. They can only be accessed by the Bot developer. There is no documentation available to extract those logs to an external database.

Hello.
Unfortunately, Watson Assistant doesn’t have such export functionality yet.

Nevertheless, technically, if you are building your own application and using Watson Assistant API v2, you can gather such information by parsing debug output.

For example, if your application sends the following message to Watson Assistant:

{
  "input": {
    "text": "unknown",
    "options": {
      "return_context": true,
      "debug": true
    }
  }
}

and receives the following respond:

{
  "output": {
    "generic": [
      {
        "response_type": "text",
        "text": "I didn't understand. You can try rephrasing."
      }
    ],
    "debug": {
      "nodes_visited": [
        {
          "dialog_node": "Anything else",
          "title": "Anything else",
          "conditions": "anything_else"
        }
      ],
      "log_messages": [],
      "branch_exited": true,
      "branch_exited_reason": "completed"
    },
    "intents": [],
    "entities": []
  },
  "context": { ... },
  "session_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}

You can conclude the intent is not recognized by the presence of path like:
debug.nodes_visited.conditions equals 'anything_else'. Of course, this approach is out of the scope of Watson Assistant Plug-in for WordPress.

• This reply was modified 6 years ago by intelahelp.

Thanks for the details !

I known that using APIs I can know the answer and be aware if an intent was recognized or not, but I do not understand why this should not be on the scope of the front. Basically, the plugin is using the APIs to get the dialog with WA, so why can not by the plugin itself the one that does some logging (for metrics and analisys) and even allow to store on and additional db the intents not recognized so you can do later on further training ?

I guess that as an alternative, I can use FaaS on the back, but I would prefer a simpler and more inmediate approach, that is why I suggested to implement it on the plugin (in fact, when I use botkit on the front intead the wp pluging, I do it on the front….)

Though centralized approach is better (Watson Assistant service gathers all the data anyway), to acquire some metrics via WordPress plug-in make sense anyway. We put this feature on the list. Thank you for bringing it in.