aws-solutions / qnabot-on-aws

AWS QnABot is a multi-channel, multi-language conversational interface (chatbot) that responds to your customer's questions, answers, and feedback. The solution allows you to deploy a fully functional chatbot across multiple channels including chat, voice, SMS and Amazon Alexa.
https://aws.amazon.com/solutions/implementations/aws-qnabot
Apache License 2.0
401 stars 253 forks source link

Enhanced logging and error messages. #668

Closed abilash44 closed 5 months ago

abilash44 commented 1 year ago

Is your feature request related to a problem? Please describe. I made a mistake of using the data id instead of the index id for the kendra index.

Describe the feature you'd like

  1. After enabling chat debug as true some error message should appear in the client side. Nothing appears I only see empty response image
  2. Some form of validation before hit save to inform the entered value is wrong.
  3. Please provide a doc section for looking at logs. There are so many services here I do not know which cloudwatch logs to look at. It will help me find out what is wrong and try fixing it myself.

Additional context I just went around in circles for a few hours creating and deleting a dozen stacks. lol.

marcburnie commented 1 year ago

Hi @abilash44 - unfortunately, the debug does not appear if there is an unhandled exception on the backend. The place you want to look for errors with the chat client is in the fulfillment lambda's log: https://us-east-1.console.aws.amazon.com/cloudwatch/home?region=us-east-1#logsV2:log-groups$3FlogGroupNameFilter$3Dfulfillment.

We're actively working on this already, so we will keep this issue open for updates.

abhirpat commented 9 months ago

Hi @abilash44 - could you please try testing this in latest QnaBot version 5.5.0? You can deploy QnaBot using template available in https://aws.amazon.com/solutions/implementations/qnabot-on-aws/. If issues persist, please provide errors in fulfillment lambda logs as mentioned above.

Looking forward to hearing from you.

abhirpat commented 5 months ago

Hi @abilash44, we haven't heard from so we are going to archive the case. As next step, I'd recommend trying out latest release v6.0.0 as we have made improvements to error message in designer and chat client. For chat client, I'd recommend to enable setting ENABLE_DEBUG_RESPONSES in the designer.

For 6.0.0 release, please refer to CHANGELOG for additional details about this release. Thank You!

If you still seen an issue, please create an example question > export > attach it as json for us to replicate the issue.