What’s the point of observability? Surely if you write good code, maintain it, handle tech debt, and administer its resources correctly, it’ll run great? Why would you need to keep a close eye on services that have already been tested and are working great? In this article I want to show how continuous monitoring of your systems closely, with tools like Checkly and Coralogix, can find problems that would have been impossible to predict or pre-optimize.

If you're using Playwright, either on its own or for synthetic monitoring with Checkly, you might have heard about writing Playwright scripts in a user-first manner. This approach focuses on interacting with the UI as a user would, such as clicking buttons or submitting forms, and then waiting for the UI to reflect the changes. However, sometimes you need to intercept and analyze the network layer to verify that your UI is getting the right responses from its supporting API.