supabase-observability
Set up comprehensive observability for Supabase integrations with metrics, traces, and alerts.Use when implementing monitoring for Supabase operations, setting up dashboards,or configuring alerting for Supabase integration health.Trigger with phrases like "supabase monitoring", "supabase metrics","supabase observability", "monitor supabase", "supabase alerts", "supabase tracing".
When & Why to Use This Skill
This Claude skill automates the implementation of comprehensive observability for Supabase integrations. It streamlines the setup of metrics collection, distributed tracing, and proactive alerting, enabling developers to maintain high performance and reliability for their database operations using industry-standard tools like Prometheus and OpenTelemetry.
Use Cases
- Performance Optimization: Monitor Supabase database latency and throughput in real-time to identify and resolve performance bottlenecks.
- Incident Management: Configure automated alerts for error rates and system health to reduce Mean Time to Recovery (MTTR) during Supabase-related service disruptions.
- End-to-End Debugging: Implement distributed tracing to track requests across microservices interacting with Supabase, simplifying the troubleshooting of complex data workflows.
- Operational Visibility: Create centralized dashboards to visualize Supabase health metrics and long-term operational trends for better capacity planning.
| name | supabase-observability |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Supabase 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.