Skip to content

Admin Operations Dashboard

Monitor platform health, revenue metrics, and system performance

Overview

The Admin Operations Dashboard gives platform administrators a real-time view of business metrics, system health, and performance data. Track MRR, subscriber growth, churn rates, and monitor system latency, data integrity, automated load test results, and AI autofix activity across Sentry errors, load tests, and CI workflows.

Accessing the Dashboard

  1. Log in with an admin account
  2. Navigate to /admin/operations/overview for business metrics
  3. Navigate to /admin/operations/health for system health

Overview Page

Revenue Metrics

At the top of the dashboard:

  • Monthly Recurring Revenue (MRR) - Total subscription revenue per month
  • Active Subscribers - Number of paying customers
  • Churn Rate - Percentage of customers who cancelled this month
  • Average Revenue Per User (ARPU) - MRR divided by active subscribers

Recent Activity

Below the metrics cards:

  • New signups - Recent user registrations
  • New subscriptions - Recently created subscription plans
  • Recent cancellations - Customers who cancelled
  • Payment failures - Failed payment attempts requiring attention

User Growth Chart

A line graph showing:

  • Total users over time
  • Growth rate trends
  • User acquisition patterns

Health Page

System Performance

  • API Response Time - Average latency for API requests
  • Database Query Time - Average time for database operations
  • Error Rate - Percentage of requests resulting in errors
  • Uptime - System availability percentage

Data Integrity Checks

Automatic checks for:

  • Orphaned records (tickets without customers, jobs without properties, etc.)
  • Missing required fields
  • Inconsistent foreign keys
  • Duplicate records

Load Test Results

Automated performance testing metrics:

  • Last Run - Timestamp of most recent load test
  • Virtual Users - Number of concurrent users simulated
  • Success Rate - Percentage of requests that completed successfully
  • Average Response Time - Median latency under load
  • Test Status - Pass/fail indicator with details

Load tests run automatically every Sunday at 12am UTC with 500 virtual users performing mixed read/write operations. See the Load Test Monitoring help article for full details.

AI Autofix Activity

Track automated bug fix attempts:

  • Sentry Errors - Production errors with AI fix attempts
  • Load Test Failures - Performance issues triggering autofixes
  • CI Build Failures - Failed builds with automated corrections
  • Success Rate - Percentage of issues successfully resolved by AI
  • Recent Fixes - List of recent autofix attempts with PR links

The dashboard shows a summary of autofix activity across all three sources, helping admins monitor how well the automated debugging system is performing.

Alert Configuration

Set up notifications for critical events:

  • Response time exceeds threshold
  • Error rate spikes
  • Data integrity issues detected
  • Payment failures
  • Subscription cancellations

Using the Dashboard

Daily Monitoring

Check the dashboard daily to:

  1. Review MRR and subscriber trends
  2. Investigate any error spikes
  3. Monitor system performance
  4. Address payment failures promptly

Weekly Reviews

Use for weekly planning:

  1. Analyze user growth patterns
  2. Review churn reasons
  3. Plan capacity based on load test results
  4. Prioritize fixes based on error frequency

Monthly Reports

Generate monthly reports using:

  1. MRR and ARPU trends
  2. Customer acquisition costs
  3. System reliability metrics
  4. Data quality improvements

Tips

  • Set up alerts - Don't rely on checking manually
  • Review daily - Catch issues before they impact users
  • Track trends - Look for patterns in metrics over time
  • Act on warnings - Data integrity checks highlight problems early

Questions

Q: How often does the dashboard update? A: Metrics update in real-time. Load test results update weekly after each Sunday test run.

Q: What's considered a healthy churn rate? A: For field service software, aim for under 5% monthly churn. Higher rates indicate product or support issues.

Q: What response time threshold should I set? A: Start with 500ms for API requests and 100ms for database queries. Adjust based on your baseline performance.

Q: How do I fix data integrity issues? A: The dashboard provides a link to fix each issue type automatically. Review and confirm before applying fixes.

Q: What does the AI autofix success rate mean? A: It shows what percentage of automatically generated bug fixes pass tests and get merged. Higher is better - aim for above 50%.

Q: How are load test results used? A: They help identify performance bottlenecks before they impact real users. Declining success rates or rising response times indicate capacity issues.

Was this helpful?
Contact Support →