Investigating errors
If you've tried interacting with the todos-frontend web app, you likely noticed that marking todos as completed often results in an error being thrown. Having run the npm run simulate command in the previous section, this error will have occurred many times. We can take a look at what's going on from the Google Cloud Console by clicking Navigation menu | Error Reporting.
Here, you'll see an overview of the errors being generated from within your project, including one originating from the todos-backend service. Clicking on the error will bring you to the error details page, which includes information such as number of occurrences, a histogram, and any related logs or stack traces:
Part of the power of Stackdriver is ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access