Observe Service Errors

This workshop has been deprecated and archived. The new Amazon EKS Workshop is now available at www.eksworkshop.com.

Let’s see if we can figure out what is causing the application filtering bug we saw earlier in this tutorial.

Given that the bug exists on the “Catalogue” page, there’s a good chance that page involves the catalogue service.

Scroll down the page to the “Service List” table and select the px-sock-shop/catalogue service.


Deep links embedded in script views allow you to easily navigate between scripts. Selecting any service name deep link will navigate you to the px/service script, which shows us the request statistics for the selected service.


The px/service script view doesn’t show any errors, but that might be because the time window isn’t large enough.

Change the start_time argument to be -30m (note the negative symbol) to make sure that the window is wide enough to include when you triggered the bug in the Sock Shop app. Once the script re-runs, you should one or more HTTP errors for the service:


If you don’t see an HTTP error, increase the time window or manually trigger the bug again in the Sock Shop web application. Make sure to re-run the script afterwards.