home / skills / bobmatnyc / claude-mpm-skills / vercel-observability

This skill helps you monitor Vercel performance and debugging through analytics, Speed Insights, logs, tracing, and alerts.

npx playbooks add skill bobmatnyc/claude-mpm-skills --skill vercel-observability

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
2.4 KB
---
name: vercel-observability
description: Vercel observability for Web Analytics, Speed Insights, logs, tracing, alerts, and observability tooling. Use when monitoring performance or debugging production behavior on Vercel.
progressive_disclosure:
  entry_point:
    summary: "Vercel observability for Web Analytics, Speed Insights, logs, tracing, alerts, and observability tooling. Use when monitoring performance or debugging production behavior on Vercel."
    when_to_use: "When working with vercel-observability or related functionality."
    quick_start: "1. Review the core concepts below. 2. Apply patterns to your use case. 3. Follow best practices for implementation."
---
# Vercel Observability Skill

---
progressive_disclosure:
  entry_point:
    summary: "Vercel observability: analytics, Speed Insights, logs, tracing, alerts, and performance monitoring."
    when_to_use:
      - "When monitoring application performance"
      - "When debugging production issues"
      - "When setting alerts for availability and errors"
    quick_start:
      - "Enable Web Analytics"
      - "Enable Speed Insights"
      - "Review logs and tracing"
      - "Configure alerts"
  token_estimate:
    entry: 90-110
    full: 3600-4700
---

## Overview

Vercel observability covers analytics, performance insights, and debugging tools for production workloads.

## Web Analytics

- Enable analytics for traffic and usage insights.

## Speed Insights

- Measure Core Web Vitals and performance metrics.
- Track real-world performance changes.

## Logs and Tracing

- Use logs for runtime errors and behavior.
- Use tracing for request performance and diagnostics.

## Alerts

- Configure alerts for operational thresholds.

## Complementary Skills

When using this skill, consider these related skills (if deployed):

- **vercel-deployments-builds**: Deployment visibility and rollback.
- **vercel-functions-runtime**: Function logs and runtime debugging.
- **vercel-networking-domains**: CDN and routing performance.

*Note: Complementary skills are optional. This skill is fully functional without them.*

## Resources

**Vercel Docs**:
- Analytics: https://vercel.com/docs/analytics
- Speed Insights: https://vercel.com/docs/speed-insights
- Logs: https://vercel.com/docs/logs
- Tracing: https://vercel.com/docs/tracing
- Alerts: https://vercel.com/docs/alerts
- Observability: https://vercel.com/docs/observability

Overview

This skill provides Vercel observability for Web Analytics, Speed Insights, logs, tracing, and alerts to help monitor and debug production applications. It collects real-world performance data, surfaces runtime errors, and lets you configure operational alerts for availability and errors. Use it to drive performance improvements and reduce time-to-resolution for incidents.

How this skill works

The skill connects Vercel observability features into a cohesive workflow: Web Analytics for traffic and user metrics, Speed Insights for Core Web Vitals and real-user performance, logs for runtime events, and tracing for request-level diagnostics. Alerts are configured against thresholds and error conditions so teams are notified when SLA or health indicators degrade. Data from these sources is used to investigate, reproduce, and remediate production issues.

When to use it

  • Monitoring production performance and Core Web Vitals
  • Investigating spikes in errors, latency, or resource usage
  • Validating performance regressions after deploys
  • Setting alerts for availability, error rates, or latency thresholds
  • Correlating user traffic patterns with backend behavior

Best practices

  • Enable Web Analytics and Speed Insights to capture both traffic and real-user performance
  • Instrument serverless functions and API routes with tracing for end-to-end request visibility
  • Centralize logs with semantic keys and consistent error codes to speed searches
  • Create actionable alerts with clear playbooks and severity levels
  • Track performance before and after deploys to identify regressions quickly

Example use cases

  • Detect a regression in Largest Contentful Paint after a release and pinpoint the responsible route
  • Alert on increased 5xx rates and use traces to find the failing dependency
  • Analyze traffic patterns to optimize caching and CDN rules for peak load
  • Aggregate logs from functions to find a recurring runtime exception and push a hotfix
  • Measure the impact of front-end changes on Core Web Vitals for conversion optimization

FAQ

Do I need other Vercel skills to use this?

No. The observability features are fully usable on their own, though pairing with deployment or runtime skills can provide additional context.

What metrics should I prioritize?

Start with Core Web Vitals (LCP, CLS, FID/INP), error rate, request latency, and throughput. Add custom business metrics as needed.