vercel-observability

jeremylongshore's avatarfrom jeremylongshore

Set up comprehensive observability for Vercel integrations with metrics, traces, and alerts.Use when implementing monitoring for Vercel operations, setting up dashboards,or configuring alerting for Vercel integration health.Trigger with phrases like "vercel monitoring", "vercel metrics","vercel observability", "monitor vercel", "vercel alerts", "vercel tracing".

⭐878stars🔀101forks📁View on GitHub🕐Updated Jan 4, 2026

When & Why to Use This Skill

This Claude skill automates the setup of comprehensive observability for Vercel integrations, incorporating metrics, distributed tracing, and proactive alerting. It streamlines the implementation of monitoring frameworks like Prometheus and OpenTelemetry to ensure high availability and performance for Vercel-based applications.

Use Cases

  • Performance Monitoring: Implementing Prometheus counters and histograms to track Vercel operation latency and success rates in real-time.
  • Distributed Tracing: Integrating OpenTelemetry to provide end-to-end visibility into request flows across Vercel services, simplifying root cause analysis.
  • Proactive Alerting: Configuring AlertManager rules to automatically notify engineering teams of critical health issues or spikes in error rates before they impact users.
  • Operational Visibility: Setting up structured JSON logging and metrics collection to power centralized Grafana dashboards for deep operational insights.
namevercel-observability
description|
allowed-toolsRead, Write, Edit
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Vercel Observability

Prerequisites

  • Prometheus or compatible metrics backend
  • OpenTelemetry SDK installed
  • Grafana or similar dashboarding tool
  • AlertManager configured

Instructions

Step 1: Set Up Metrics Collection

Implement Prometheus counters, histograms, and gauges for key operations.

Step 2: Add Distributed Tracing

Integrate OpenTelemetry for end-to-end request tracing.

Step 3: Configure Structured Logging

Set up JSON logging with consistent field names.

Step 4: Create Alert Rules

Define Prometheus alerting rules for error rates and latency.

Output

  • Metrics collection enabled
  • Distributed tracing configured
  • Structured logging implemented
  • Alert rules deployed

Error Handling

See {baseDir}/references/errors.md for comprehensive error handling.

Examples

See {baseDir}/references/examples.md for detailed examples.

Resources