Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Adds a session attribute to count missed utterances #732

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

richhaase
Copy link

Issue #, if available:

Description of changes:

This PR adds a session attribute that counts the number of consecutive missed utterances. This information allows us to exhibit different behavior depending on how many times a user asks a question that the QnA Bot is unable to answer.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@abhirpat
Copy link
Member

abhirpat commented Jun 7, 2024

Thank you for your submission @richhaase. Could you please elaborate where and how you are using this information ? Have you had a chance to explore OpenSearch Dashboards for chat usage information like No Hits response satisfy your requirements?

@abhirpat
Copy link
Member

abhirpat commented Jul 8, 2024

Hi @richhaase, following-up on my previous message. Currently, no_hits are displayed in OpenSearch Dashboards > QnABot
Dashboard > No hits. If you're still needing this, please elaborate the use-case.

@israelias
Copy link

You can also just consider adding a lambda to the no_hits module that does the same thing plus more, in case you're trying to timeout and/or super-error-handle false on qnabot_gotanswer. But also consider how/why/when you would clear the count in case Kendra fallback is plugged to play as a feature on tie breaker, where every answer is not a hit -- to name one potential side effect to drill through. In any case I think your numerics have to be set as string values for sessionAttributes

@abhirpat abhirpat self-assigned this Jul 15, 2024
@abhirpat abhirpat removed their assignment Sep 4, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants