In what table can I find user utterances?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
â03-10-2022 08:00 AM
For the longest time, I've been using the interaction_log table to quickly and simply query real user utterances - i.e. "how many people typed in "x" to VA?" - but I'm finally asking for help after being frustrated by the 40 character limit on the Utterance field on that table which truncates many utterances.
I'm sure one option is to simply expand the max length on that table - no idea why it's so small ootb - but that only addresses data going forward and still I have to imagine that there's a better ootb table for this real data.
I'm aware of the open_nlu_predict_intent_feedback table which is incredibly valuable in debugging user utterances and their predictions - but the problem with this table is that individual utterance entries are not unique. i.e. if one utterance results in two predictions, there will be two entries in the table.
For this scenario I'm asking about, I just want to know each utterance that's used - I don't care about the predictions nor do I want to do data manipulation/exports to cull the non-unique entries. This may be a really simple and obvious question, but what table gets me this data?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
â04-04-2022 03:12 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
â05-04-2022 07:09 AM
Hello Chris,
There is a known defect fixed in San Diego where a Production instance with Read Replicas on the database, if the "com.glide.nlu.proxy" plugin is activated, the records are not always showing up in table [open_nlu_predict_log]. Which version of the ServiceNow Platform are you on?
Best regards,
Brian

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
â05-09-2022 07:03 AM
Back when I posted originally we were on Quebec, but all in on San Diego now.
Is that defect even relevant here? I want to see all utterances in one table but if the open_nlu_predict_log table is rotated, then even if we were experiencing that defect, would it even matter since most of the historical data wasn't in that one table?