vercel logs --environment production --status-code 500 --json

vercel curl --trace --json /api/hello

# Most metrics require Observability Plus
vercel metrics list

You can use Observability on all plans to monitor your projects. Observability Plus is available on Pro and Enterprise teams, providing additional features and metrics, higher limits, and increased retention.

Use logs to find failing requests, traces to inspect one request path, and metrics to compare behavior over time. Use JSON output when a script or coding agent needs structured data.

How you use Observability depends on the needs of your project, for example, perhaps builds are taking longer than expected, or your Vercel Functions seem to be increasing in cost. A brief overview of how you might use the tab would be:

1. Decide what feature you want to investigate. For example, Vercel Functions.
2. Use the date picker or the time range selector to choose the time period you want to investigate. Users on Observability Plus will have a longer retention period and more granular data.
3. Let's investigate our graphs in more detail, for example, Error Rate. Click and drag to select a period of time and press the Zoom In button.

4. Then, from the list of routes below, choose to reorder either based on the error rate or the duration to get an idea of which routes are causing the most issues.
5. To learn more about specific routes, click on the route.
6. The functions view will show you the performance of each route or function, including details about the function, latency, paths, and External APIs. Note that Latency and breakdown by path are only available for Observability Plus users.
7. The function view also provides a direct link to the logs for that function, enabling you to pinpoint the cause of the issue.

Observability provides different sections of features and traffic sources that help you monitor, analyze, and manage your applications either at the team or the project level. The following table shows their availability at each level:

Vercel tracks the following event types for Observability:

• Edge Requests
• Vercel Function Invocations
• External API Requests
• Routing Middleware Invocations
• AI Gateway Requests

Vercel creates one or more of these events each time a request is made to your site. Depending on your application and configuration a single request to Vercel might be:

• 1 edge request event if it's cached.
• 1 Edge Request, 1 Middleware, 1 Function Invocation, 2 External API calls, and 1 AI Gateway request, for a total of 6 events.
• 1 edge request event if it's a static asset.

Vercel tracks events at the team level, counting them across all projects in the team.

If you've excluded specific projects from Observability Plus, those projects won't generate metered events.

Users on all plans can use Observability at no additional cost, with some limitations. The Observability section in the sidebar is available on the project dashboard for all projects in the team.

Pro and Enterprise teams can use Observability Plus for additional features, higher limits, and increased retention.

You can also manage which projects are included in your Observability Plus subscription to control costs.

For more information on pricing, see Pricing.

For step-by-step debugging workflows using the Vercel CLI with Observability data, see Debugging production 500 errors.