These are issues caused by how the client communicates with the server, rather than by the server's core application logic. Think unexpected connection resets, semantically invalid HTTP requests, syntactically invalid HTTP requests, and the like. When we talk about 'client' errors, I'm talking about errors that are typically blamed on bad client behavior. These don't tell the whole story, as there's a whole world of errors that matter to the backend, and whose root cause lies in the server itself, but which surface as client errors, and never get reported. In many cases though, those checks alone can offer a false confidence to teams, who assume that no explicit server errors means that everything is working fine. For this post, I want to go beyond these surface checks, but that's not to say they're unimportant: before you do anything else here, I'd strongly recommend having that fundamental monitoring in place. Most backend monitoring and logging will detect and report on explicit server failures, from tracking the number of 5xx HTTP error responses that you send to reporting thrown exceptions to services like Sentry. With so many possible forms of failure though, there's some critical cases that can fall through the cracks. When you're building and running a web service, keeping an eye on errors is essential to finding bugs, and understanding the experience of your end users (and hopefully even improving it). There's a lot that can go wrong when talking to servers on the web.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |