Although AWS makes it very easy to deploy a QnA bot, AWS makes it almost impossible to analyze the data received. Unless of course you love to dig through dozens of CloudWatch logs in un-human type reports.
Seriously, the designers of the UX/UI really need very long vacations as many of the designs are convoluted, and too complex to waste time attempting to figure out. Ummm just like their newly designed UI console.
QnA Bot Install Tips
Step 1. Is to deploy via CFT per the AWS post. You may want to dry-run a demo first, and consider using the “public” client, and keep the nodes down to 1. [Practically everything on AWS = $$$$]. Our demo video uses the very basic options.
Step 2. Bookmark your URLs from the output of the CFT as shown in the image. Drill-down on the plain completion title, and go to the outputs tab.
Step 3. Your password and login link will be sent to the email address you provided during deployment, so don’t use a placebo.
Step 4. [Important!] Create a test question, and test the bot’s response first! This will generate the required output log for the next section. You must use the QnA client to test, not the designer UI testing tool.
A51 AWS QnA Reports
aMiSTACX to the rescue! Yes, we eat our own dog food, and look for ways to improve A51 all of the time. Since we have been using AWS QnA bots for a few years, and when AWS changed their reporting into a big mess, we decided to develop a human friendly reporting tool in A51.
Step 5. Add the Reports ARN and the Designer output link to your A51 user profile under your specific A51 account.
ARN can be found in CloudWatch >> Log Group >> Fulfilment
Drill-down to get the ARN.
Step 6. Just set a date filter and go! You’ll polled questions asked and answers, and all sorted by date and time. We even included a handy export feature, and quick-link to your designer dashboard.
A very cool tool to save you a lot of time, and keep your Bot productive!!