Velo: Working with the Monitoring Dashboard

Visit the Velo by Wix website to onboard and continue learning.
When managing a site with backend code and Wix Data API requests, it's important to monitor the code's performance. That way, you can make sure your visitors have the best possible experience. This article describes how to use Velo's built-in Monitoring dashboard as a solution for monitoring site performance. 
In addition to this tool, you can also monitor site performance using site logs. These are internal and external logging tools that allow you to track and store your live site logs.
Note:To use the Monitoring dashboard, you must enable Velo Dev Mode for your site.

About the Monitoring dashboard

The Monitoring dashboard helps site owners, in-house developers, and other service providers do the following:
  • Track the performance of your backend code and data requests over time.
  • Monitor the amount of storage space your collections are using.
  • Detect when your site isn't performing as expected.
  • Troubleshoot and determine the causes of a site not functioning well. Is it because of a temporary problem or an ongoing issue? Is it because a quota was reached? Did a Wix or a user error occur?

Access the Monitoring dashboard

You can access the Monitoring dashboard from the Editor or your site's dashboard.

From the Editor

  1. In the Velo Sidebar, select the Developer Tools tab. 
  2. In the Monitoring section, select Monitoring.

From your site's dashboard

  1. In the sidebar, hover over Developer Tools.
  2. Select Monitoring.

Understand the dashboard

The Monitoring dashboard is divided into several sections:


The top section of the dashboard displays a high-level overview of backend requests, data requests, and collection storage on your site. Exclamation icons image indicate which parts of the site performance need attention. The section includes links for more guidance.
Overview bar


The middle section of the dashboard displays a breakdown of your site's performance. There are separate tabs that display information about backend requests, data requests, and collection storage. When you open the dashboard, the Backend Requests breakdown displays by default. To see one of the other breakdowns, click the appropriate tab.
Breakdown tabs
Here's what you'll find in each of the breakdowns:

Backend Requests

This breakdown displays information about requests to your backend code made from your site's frontend. Backend requests include HTTP functions, router hooks, and web module calls made from your frontend code. By default, the dashboard displays aggregated information about all the requests made to all the backend functions on your site. You can use the filters to display request data for specific functions and time periods.
Backend request filters
The Backend Requests breakdown includes these panels:

Data Requests

This breakdown displays information about data requests made by your site. This includes requests from your site's code to the Wix Data API as well as requests made by the Content Manager and dynamic pages. Data requests include querying your site's collections, as well as saving and deleting data. By default, the dashboard displays aggregated information about all the requests made to all the collections on your site. You can use the filters to display request data for specific collections, operations, and time periods.
Data request filters
The Data Requests breakdown includes these panels:

Content Collection Storage

This breakdown displays the amount of data stored in your site's content collections. Each Wix site can store up to 10 GB of data in its collections. This quota doesn't apply to external database collections or Wix app collections. It also doesn't apply to other media stored on your site or documents and multimedia referenced from a collection.
Learn more about the content collection storage quota.
The Content Collection Storage breakdown has only one panel, Collection storage breakdown. This table lists the largest collections on your site, indicating both the collection name and ID. You can resize and sort each column.
Collection storage breakdown

Further Guidance

The bottom of each breakdown section in the dashboard has two links. The first is to a guide for optimizing your site to prevent failed requests or minimize storage usage. The second is a link for connecting your site to Google Operations. If you have already connected your site, the link opens Google Operations.
Optimize & Google operations panel

Example: Use the Dashboard

Here is an example of how you can use the dashboard to solve an actual issue that might arise.
  1. In the overview, notice a peak of 622 failed backend requests over the past 30 days.

    Example backend requests overview

    Every site is different, but ideally, we want 0 failed requests. 622 is definitely a number that we want to investigate.
  2. Let's look at the Failed Requests breakdown to detect whether the main reason for the issue is RPM throttling, timed-out requests, or errors. We can see that most of the failed requests are timed-out (turquoise).

    Example failed requests

  3. Our next step is to look at the graphs and table for specific functions to see if we can identify problematic ones. We noted in the previous step that timeouts are our issue. To see the functions with the most timeouts, click the Timed-Out column in the Top Backend Functions table, to sort in descending order.

    Example top backend functions

  4. The getUserDetails function has timed out the most. Focus on this function by filtering for it. Filtering affects all the charts and the table.
  5. We can view the Request Durations graph to see the median duration of the function. This gives us a better sense of the durations for the getUserDetails function.   
  6. We can also look at the Failed Requests chart again for this function to understand if the problem is ongoing or if it peaks on a specific day.
  7. View site logs in Google Operations to see if you find information about why requests are taking so long.
  8. Now that we've identified the problematic function, we can start recognizing any quotas that the site reached and looking for possible solutions. Solutions might include batching the requests, combining Wix Data requests, and/or upgrading to a premium Wix site. Optimize your code according to the suggestions and publish your site.
  9. Monitor your site using the Monitoring dashboard in the coming days to make sure the problem is resolved.

Did this help?


Hire a Wix Partner

Get help with your website's design, marketing and small tasks from a professional freelancer or agency.
Start Now