Velo: Working with the Monitoring Dashboard

The Monitoring Dashboard helps you analyze a site's performance for backend code and data operations, and track its CMS collections. Use it to improve site visitors' experience by monitoring request performance, identifying issues, and optimizing site code.

The Monitoring Dashboard has the following tabs:

• Data requests: Tracks calls to a site's CMS collections.
• Backend requests: Tracks backend code performance and errors.
• CMS collection storage: Tracks a site's current storage usage relative to its quotas.

Data requests

The Data requests tab displays information about calls to a site's CMS collections. Every time you access your data, whether to read or write it, you make a data request.

The Data requests tab includes the following sections:

• Overview: Displays the number of successful and unsuccessful data requests, along with the error rate. When viewing the default 7-day period, the dashboard compares the error rate to the previous 7 days.
• All data requests: Displays a graph of all requests made during the selected time period. Successful requests appear in blue and failed requests appear in red.
• Data requests by operation: Breaks down request information by collection and operation type. Each row represents a unique pairing. The table includes the following columns:

Column	Description
Collection	The collection name. If the collection doesn't exist or multiple collections share the same name, the collection ID appears.
Operation	The type of operation performed, such as find, insert, or update.
Count	The number of times this operation ran on this collection during the time period.
Error rate	The percentage of failed requests.
Cache rate	The percentage of requests served from cache.
Duration p50	The median request duration in milliseconds.
Duration p95	The 95th percentile request duration in milliseconds, representing slower requests.

Click a row to navigate to a page with more details about requests for that specific collection and operation pairing.

To minimize failed data requests:

• Simplify complex queries.
• Add proper indexes to collections.
• Use efficient query patterns.
• Implement caching for frequently accessed data.
• Consider pagination for large result sets.

Backend requests

To minimize failed backend requests:

For timeout issues:

• Reduce the number of operations in your method.
• Use caching to avoid repeated calculations.
• Optimize database queries with proper filtering and sorting.

For RPM throttling:

• Implement request batching.
• Add delays between rapid requests.
• Consider upgrading your premium plan for higher limits.

CMS collection storage

Each Wix site can have a maximum of 1,000 collections and 10 million collection items, which can take up no more than 100 GB of storage space. The CMS collection storage tab lets you know how close a site is to these quotas, and lists CMS collections that Wix users created on the site.

These don't count toward the storage space quota:

• External database collections.
• Wix app collections.
• Media files stored separately on a site.
• Referenced documents and multimedia.

See also

• About Wix Logs
• Data features
• Compute features
• About caching
• Best practices for building a site
• Best practices for improving site performance