Manage and optimize usage for Observability

The Observability section covers usage for Observability, Monitoring, Web Analytics, and Speed insights.

The Events chart shows the number of page views and custom events that were tracked across all of your projects. You can filter the data by Count or Projects.

Hobby teams include 50,000 events per month. Vercel bills Pro, Pro with Web Analytics Plus, and Enterprise teams based on collected event usage. You can see the total number of events used by your team by selecting Count in the chart.

• Your usage is based on the total number of events used across all projects within your team. You can see this number by selecting Projects in the chart, which will allow you to figure out which projects are using the most events and can therefore be optimized
• Reduce the amount of custom events they send. Users can find the most sent events in the events panel in Web Analytics
• Use beforeSend to exclude page views and events that might not be relevant

Vercel charges an initial set amount for each Pro project where you enable Speed Insights. Hobby teams include 10,000 events per month. Vercel bills Pro, Pro with Web Analytics Plus, and Enterprise teams based on collected event usage.

Events are single units of information that represent a measurement of a specific Web Vital metric during a user's visit to your website. Vercel collects events on hard navigations.

• To reduce cost, change the sample rate at a project level by using the @vercel/speed-insights package as explained in Sample rate. You can also set a cost limit under your team's Billing settings page to stop event collection for the rest of the billing period after your team reaches the limit
• Use beforeSend to exclude page views and events that might not be relevant
• Disable Speed Insights for projects that no longer need it. This stops Vercel from collecting events for a project

Vercel creates an event each time a request is made to your website. These events include unique parameters such as execution time and bandwidth used. For a complete list, see the visualize and group by docs.

Monitoring is deprecated and no longer exposed as a current top-level pricing resource. If you are still using Monitoring, migrate to Observability Plus for usage-based pricing and current observability features.

You can also view the number of events used by each project in your team by selecting Projects in the chart. This will show you the number of events used by each project in your team, allowing you to optimize your usage.

Because events are based on the amount of requests to your site, there is no way to optimize the number of events used.

You can optimize your log drains usage by:

• Filtering by environment: You can filter logs by environment to reduce the number of logs sent to your log drain. By filtering by only your production environment you can avoid the costs of sending logs from your preview deployments
• Sampling rate: You can reduce the number of logs sent to your log drain by using a sampling rate. This will send only a percentage of logs to your log drain, reducing the number of logs sent and the cost of your log drain

Vercel creates one or many events each time a request is made to your website. To learn more, see Events.

You pay for Observability Plus based on the total number of events generated by projects where Observability Plus is enabled.

The Observability chart allows you to view by the total Count, Event Type, or Projects over the selected time period.

To reduce Observability Plus costs, you can exclude specific projects that don't need advanced observability. Excluded projects revert to the free tier and stop generating metered Observability Plus events.

You can manage project inclusions from your team's Billing settings or from a project's Observability dashboard. See Managing projects for details.