Display comprehensive deployment and performance metrics dashboard for Cloudflare Workers and Pages with GitHub Actions CI/CD integration
Displays comprehensive deployment and performance metrics for Cloudflare Workers and Pages with GitHub Actions CI
/plugin marketplace add greyhaven-ai/claude-code-config/plugin install cloudflare-deployment-observability@grey-haven-pluginsDisplay a comprehensive metrics dashboard for Cloudflare Workers and Pages deployments, including deployment metrics, performance data, CI/CD pipeline health, and Core Web Vitals.
Deployment Metrics
Performance Metrics
CI/CD Pipeline Metrics
Core Web Vitals
# Show all metrics
/cf-metrics-dashboard
# Specific time range
/cf-metrics-dashboard --range 7d
/cf-metrics-dashboard --range 24h
/cf-metrics-dashboard --range 30d
# Specific worker
/cf-metrics-dashboard --worker production-worker
# Specific environment
/cf-metrics-dashboard --env production
# Compare deployments
/cf-metrics-dashboard --compare abc123 xyz789
# Export to file
/cf-metrics-dashboard --export dashboard.json
# Specific metric groups
/cf-metrics-dashboard --metrics deployment,performance
/cf-metrics-dashboard --metrics cicd
/cf-metrics-dashboard --metrics web-vitals
# Cloudflare Deployment Metrics Dashboard
**Worker**: production-worker
**Environment**: production
**Period**: Last 7 days
**Generated**: 2025-01-15 10:30:00 UTC
---
## š Executive Summary
| Metric | Value | Trend | Status |
|--------|-------|-------|--------|
| Deployment Success Rate | 96% | ā +2% | ā
Good |
| Average Deployment Time | 2m 45s | ā -15s | ā
Good |
| Error Rate | 0.08% | ā -0.02% | ā
Good |
| P95 Latency | 125ms | ā +10ms | ā ļø Warning |
| Core Web Vitals Score | 92/100 | ā 0 | ā
Good |
---
## š Deployment Metrics
### Deployment Frequency
Week view: Mon āāāāāāāāāāāā 12 deployments Tue āāāāāā 6 deployments Wed āāāāāāāāā 9 deployments Thu āāāāāāāāāāā 11 deployments Fri āāāāāāāā 8 deployments Sat āāāā 4 deployments Sun āā 2 deployments
Total: 52 deployments Average: 7.4 deployments/day
### Deployment Success Rate
Last 7 days: 96% (50/52 successful) Last 30 days: 94% (198/210 successful)
Trend: ā Improving
### Deployment Duration
| Metric | Current | Previous | Change |
|--------|---------|----------|--------|
| Mean | 2m 45s | 3m 00s | ā -15s |
| P95 | 4m 30s | 5m 00s | ā -30s |
| P99 | 6m 15s | 7m 00s | ā -45s |
| Max | 8m 20s | 9m 30s | ā -1m 10s |
**Trend**: ā
Improving (15% faster)
### Recent Deployments
| Time | Status | Duration | Commit | Environment |
|------|--------|----------|--------|-------------|
| 2h ago | ā
Success | 2m 30s | abc123 | production |
| 4h ago | ā
Success | 2m 45s | def456 | staging |
| 6h ago | ā Failed | 1m 20s | ghi789 | production |
| 8h ago | ā
Success | 3m 10s | jkl012 | production |
| 10h ago | ā
Success | 2m 55s | mno345 | staging |
### Rollback Activity
Total rollbacks (7d): 2 Rollback rate: 3.8%
Reasons:
Mean time to rollback: 5m 30s
---
## ā” Performance Metrics
### Request Latency
Current (last hour): p50: 45ms āāāāāāāāāāāāāāāāāāāā p75: 82ms āāāāāāāāāāāāāāāāāāāā p95: 125ms āāāāāāāāāāāāāāāāāāāā p99: 245ms āāāāāāāāāāāāāāāāāāāā
Target thresholds: p50: <50ms ā Met p95: <200ms ā Met p99: <500ms ā Met
**7-day trend**:
Day 1: p95=115ms āāāāāāāāāāāāā Day 2: p95=118ms āāāāāāāāāāāāāā Day 3: p95=120ms āāāāāāāāāāāāāā Day 4: p95=125ms āāāāāāāāāāāāāā Day 5: p95=122ms āāāāāāāāāāāāāā Day 6: p95=125ms āāāāāāāāāāāāāā Day 7: p95=125ms āāāāāāāāāāāāāā
Trend: ā Slight increase (+10ms)
### Request Volume
Requests/second (current): 1,245 rps Requests/day (average): 107M requests
Peak: 2,180 rps (09:00 UTC) Trough: 340 rps (03:00 UTC)
### Error Rates
| Error Type | Count | Rate | Trend |
|------------|-------|------|-------|
| 5xx errors | 850 | 0.08% | ā Good |
| 4xx errors | 12,400 | 1.16% | ā Stable |
| Timeouts | 120 | 0.01% | ā Good |
| Total | 13,370 | 1.25% | ā Good |
**Target**: <1% error rate for 5xx errors ā
Met
### Cold Start Analysis
Cold starts (7d): 3,420 Cold start rate: 0.32% of requests
Duration distribution: p50: 180ms āāāāāāāāāāāāāāāāāāāā p95: 350ms āāāāāāāāāāāāāāāāāāāā p99: 520ms āāāāāāāāāāāāāāāāāāāā
Impact: Minimal (<0.5% of requests)
### Bundle Size
Current: 512 KB āāāāāāāāāāāāāāāāāāāā Maximum: 750 KB āāāāāāāāāāāāāāāāāāāā Percentage: 68% of limit
7-day trend: Day 1: 505 KB āāāāāāāāāāāāāāāāāāāā Day 2: 508 KB āāāāāāāāāāāāāāāāāāāā Day 3: 510 KB āāāāāāāāāāāāāāāāāāāā Day 4: 512 KB āāāāāāāāāāāāāāāāāāāā Day 5: 512 KB āāāāāāāāāāāāāāāāāāāā Day 6: 512 KB āāāāāāāāāāāāāāāāāāāā Day 7: 512 KB āāāāāāāāāāāāāāāāāāāā
Change: +7 KB (+1.4%) Status: ā Under control
---
## š CI/CD Pipeline Metrics
### GitHub Actions Performance
Workflow: Deploy to Cloudflare Total runs (7d): 52 Success rate: 96% (50/52)
Duration breakdown: āā Build job: 2m 15s (50%) āā Test job: 1m 30s (33%) āā Deploy job: 45s (17%)
Total average: 4m 30s
### Job-Level Performance
| Job | Avg Duration | Success Rate | Trend |
|-----|--------------|--------------|-------|
| Build | 2m 15s | 98% | ā -10s |
| Test | 1m 30s | 96% | ā 0s |
| Deploy | 45s | 100% | ā -5s |
### Cache Effectiveness
npm cache hit rate: 87% Build cache hit rate: 72%
Time saved by caching:
Total time saved per run: 2m 50s
### GitHub Actions Minutes Usage
Total minutes (7d): 234 minutes Average per run: 4.5 minutes Projected monthly: ~1,000 minutes
Cost (estimated): $0.00 (within free tier)
### Failure Analysis
Failed runs (7d): 2
Failure breakdown:
Mean time to fix: 15 minutes
---
## š Core Web Vitals
### Overall Score: 92/100 ā
| Metric | Value | Target | Status | Trend |
|--------|-------|--------|--------|-------|
| LCP (p75) | 1.8s | <2.5s | ā
Good | ā Stable |
| FID (p75) | 45ms | <100ms | ā
Good | ā Better |
| CLS (p75) | 0.05 | <0.1 | ā
Good | ā Stable |
| FCP (p75) | 1.2s | <1.8s | ā
Good | ā Stable |
| TTFB (p75) | 420ms | <600ms | ā
Good | ā +20ms |
### LCP (Largest Contentful Paint)
Distribution: Good (<2.5s): āāāāāāāāāāāāāāāāāāāā 89% ā Needs work (2.5-4s): āāā 8% ā ļø Poor (>4s): ā 3% ā
p75 value: 1.8s ā Good Target: <2.5s
### FID (First Input Delay)
Distribution: Good (<100ms): āāāāāāāāāāāāāāāāāāāā 95% ā Needs work (100-300ms): ā 4% ā ļø Poor (>300ms): ā 1% ā
p75 value: 45ms ā Good Target: <100ms
### CLS (Cumulative Layout Shift)
Distribution: Good (<0.1): āāāāāāāāāāāāāāāāāāāā 92% ā Needs work (0.1-0.25): āā 6% ā ļø Poor (>0.25): ā 2% ā
p75 value: 0.05 ā Good Target: <0.1
### Geographic Performance
| Region | LCP | FID | CLS | Score |
|--------|-----|-----|-----|-------|
| US-East | 1.6s | 42ms | 0.04 | 95/100 ā
|
| US-West | 1.7s | 44ms | 0.05 | 94/100 ā
|
| EU-West | 1.9s | 48ms | 0.06 | 91/100 ā
|
| APAC | 2.2s | 55ms | 0.07 | 88/100 ā ļø |
**Note**: APAC region slightly slower, still meeting targets
---
## š Trends & Insights
### Key Findings
1. ā
Deployment speed improved 15% over last week
2. ā ļø P95 latency increased by 10ms (monitoring)
3. ā
Error rate decreased by 0.02%
4. ā
Core Web Vitals stable and meeting targets
5. ā
CI/CD pipeline optimized with caching
### Performance Regressions Detected
None. All metrics within acceptable thresholds.
### Recommendations
1. **Medium Priority**: Investigate P95 latency increase
- Started: 3 days ago
- Impact: +10ms (still within target)
- Action: Review recent code changes
2. **Low Priority**: Optimize APAC region performance
- LCP slightly higher (2.2s vs 1.8s average)
- Still meeting targets (<2.5s)
- Action: Consider regional caching strategy
### Upcoming Alerts
ā ļø Bundle size approaching 70% of limit
- Current: 512 KB / 750 KB
- Action: Plan bundle size optimization
---
## š Historical Comparison
### vs. Last Week
| Metric | Current | Last Week | Change |
|--------|---------|-----------|--------|
| Deployment frequency | 52 | 48 | +4 (+8%) |
| Success rate | 96% | 94% | +2% |
| Avg deployment time | 2m 45s | 3m 00s | -15s (-8%) |
| Error rate | 0.08% | 0.10% | -0.02% |
| P95 latency | 125ms | 115ms | +10ms (+9%) |
### vs. Last Month
| Metric | Current | Last Month | Change |
|--------|---------|------------|--------|
| Deployment frequency | 52/wk | 45/wk | +7 (+16%) |
| Success rate | 96% | 92% | +4% |
| Avg deployment time | 2m 45s | 3m 30s | -45s (-21%) |
| Error rate | 0.08% | 0.12% | -0.04% |
| P95 latency | 125ms | 130ms | -5ms (-4%) |
---
## šÆ SLO Status
### Service Level Objectives
| SLO | Target | Current | Status | Remaining Error Budget |
|-----|--------|---------|--------|------------------------|
| Availability | 99.9% | 99.92% | ā
Met | 80% remaining |
| P95 Latency | <200ms | 125ms | ā
Met | 37% used |
| Error Rate | <1% | 0.08% | ā
Met | 92% remaining |
| Deployment Success | >95% | 96% | ā
Met | 20% buffer |
**Error Budget Status**: ā
Healthy
- 80% error budget remaining
- Current burn rate: Low
- Projected to meet SLOs for next 30 days
---
## š Active Alerts
No active alerts. All systems operational. ā
---
## š” Next Actions
1. Continue monitoring P95 latency trend
2. Review code changes from last 3 days
3. Plan bundle size optimization for next sprint
4. Consider APAC region caching improvements
---
**Report Generated**: 2025-01-15 10:30:00 UTC
**Next Update**: Automatic (every hour) or run `/cf-metrics-dashboard` anytime
Compare different deployments:
/cf-metrics-dashboard --compare abc123 xyz789
Output shows side-by-side comparison with deltas.
# Last 24 hours
/cf-metrics-dashboard --range 24h
# Last 7 days (default)
/cf-metrics-dashboard --range 7d
# Last 30 days
/cf-metrics-dashboard --range 30d
# Custom range
/cf-metrics-dashboard --from 2025-01-01 --to 2025-01-15
Show specific metric categories:
# Only deployment metrics
/cf-metrics-dashboard --metrics deployment
# Only performance metrics
/cf-metrics-dashboard --metrics performance
# Multiple categories
/cf-metrics-dashboard --metrics deployment,performance,cicd
# Export to JSON
/cf-metrics-dashboard --export dashboard.json
# Export to CSV
/cf-metrics-dashboard --export metrics.csv
# Send to monitoring platform
/cf-metrics-dashboard --export datadog
Send metrics to external platforms:
Set up alerts based on thresholds:
{
"alerts": [
{
"metric": "deployment_success_rate",
"threshold": 0.95,
"operator": "<",
"action": "notify_slack"
},
{
"metric": "p95_latency_ms",
"threshold": 200,
"operator": ">",
"action": "create_incident"
}
]
}
Regular Review
Threshold Monitoring
Historical Analysis
Actionable Insights
/cf-deployment-status - Check current deployment status/cf-logs-analyze - Analyze logs for errorscloudflare-performance-tracker agent for detailed performance analysiscloudflare-deployment-monitor agent for active monitoringCustomize dashboard settings:
// .claude/settings.json
{
"cloudflare-metrics": {
"default_range": "7d",
"default_worker": "production-worker",
"refresh_interval": "1h",
"thresholds": {
"p95_latency_ms": 200,
"error_rate": 0.01,
"deployment_success_rate": 0.95
},
"web_vitals_targets": {
"lcp": 2.5,
"fid": 100,
"cls": 0.1
}
}
}
No metrics available:
Incomplete data:
Metrics don't match other tools: