DOCS
clock Last Modified: Oct 23, 2018

Frontend and Backend

Last modified: October 23, 2018

The frontend and backend responses make it easy to monitor the responses received by both the public site visitors and logged in users, to ensure they do not encounter errors when accessing the site.

Frontend

This chart represents the number of responses received by public site visitors (non-logged in users), including bots, split by categories: 200 - success, 300 - redirects, 400 - not found or forbidden (client errors), and 500 - server errors. For more information about what these error represent, check our article Error Pages — What They Mean and How to Get What You Want.

The number of responses received by public site visitors, including bots
info The number of responses received by public site visitors, including bots

You can disable or enable one of these categories from appearing on the chart by simply clicking it. For example, in the screenshot above, the Client and Server errors can barely be seen, so you can unselect the Success and Redirect metrics in order to see them better:

Frontend responses - only client errors and server errors enabled
info Frontend responses - only client errors and server errors enabled

You also have a lot of time filter possibilities, from the last minute to the last 6 months, along with the possibility of comparing the frontend requests with another metric, e.g. compare them with the backend ones. All the information in categorized by timezone, based on your computer’s time and location settings.

Backend

Along with the Front-end requests, you have a chart showing the Back-end requests, which are the number of responses returned by logged-in users. This is also split by the following categories: 200 - success, 300 - redirects, 400 - not found or forbidden (client errors), and 500 - server errors.

The number of responses returned by logged-in users, split by types
info The number of responses returned by logged-in users, split by types

You can disable or enable the display of one of these categories by simply clicking on it.

You have a lot of time filtering possibilities, from the last minute to the last 6 months, along with the possibility of comparing these requests with another metric, e.g. compare them with the Front-end ones.

Comparing backend responses with the frontend ones
info Comparing backend responses with the frontend ones

All the information in categorized by timezone, based on your computer’s time and location settings.

FAQs

Why are readers reporting errors on the site?

At Presslabs, we provide Frontend stats, showing you the number of responses received by public site visitors, including both client errors and server errors.

For example, you can select the last 24 hours as a time metric, and disable the success and redirect stats to see the errors properly. You can view these errors hourly, 10 minutes apart or 1 minute apart. In the screenshot below, you can see that the number of client errors is merely 1% of the total number of responses received by public site visitors, while the server errors are so low they are estimated close to 0%.

Frontend responses for the last 24 hours, with success and redirect stats disabled
info Frontend responses for the last 24 hours, with success and redirect stats disabled

If you see an unusually high number of server side errors (usually 500, 502, 504 errors), the first thing to do is check our status page to see if there are any planned maintenance activities, outages or service disruptions of any kind on our platform. If this is not the case, the next step is to check the commits that have been made to your site’s source code at git.presslabs.net -> Your site’s repository -> Commits. For more information, drop us an email at support@presslabs.com and we can provide you with more details about these errors.