Skip to main content

Alerting & Monitoring Tickets

Mobile Visibility​

📋 JIRA-DEVOPS-001: Implement Mobile App Cloud Logging​

Status: DRAFT - Not Created Description: The logs from mobile need to be sent to the cloud asynchronously, so that way we have full visibility on the user experience.

Tasks:

  • Design mobile logging architecture
  • Implement async log shipping from mobile
  • Create mobile log aggregation in GCP
  • Add mobile error tracking
  • Build mobile analytics dashboard
  • Implement mobile crash reporting

📋 JIRA-DEVOPS-002: Build User Journey Tracing System​

Status: DRAFT - Not Created Description: Implement a mechanism for a user to be able to have a full trace of their journey in the app. This is tied to logs from mobile being pushed to backend, giving us full trace of issues so we know immediately if something is working or not.

Tasks:

  • Design user session tracking architecture
  • Correlate mobile and backend logs
  • Create user journey visualization
  • Build user-specific debugging tools
  • Implement journey-based alerting
  • Add user impact analysis

System Performance​

📋 JIRA-DEVOPS-003: Create System Performance Dashboard​

Status: DRAFT - Not Created Description: Implement a page where we see the speed of the system in terms of handling requests and responses.

Tasks:

  • Design performance metrics collection
  • Implement latency tracking
  • Add throughput monitoring
  • Create performance dashboard UI
  • Add historical performance trends
  • Implement performance alerting

Alerting Infrastructure​

✅ JIRA-DEVOPS-004: Implement GCP Log-Based Alerting​

Status: CREATED - In Progress Jira Ticket: ED-6 Description: Implement an alerting mechanism on GCP based on logs so that way we know immediately if we have an issue.

Tasks:

  • Define alert criteria and thresholds
  • Configure log-based metrics in GCP
  • Set up alerting policies
  • Create alert routing rules
  • Implement alert escalation
  • Test alert delivery channels

✅ JIRA-DEVOPS-005: Implement Comprehensive Health Check System​

Status: CREATED - In Progress Jira Tickets:

  • ED-3 - Uptime and Database Health Checks
  • ED-4 - PubSub Health Check
  • ED-5 - Email Service Health Check Description: Implement a full health check monitoring system for everything - database, pub/sub, emailing, logging. Currently there's no unified way to verify operational status.

Tasks:

  • Create /health endpoints for all services
  • Add database connectivity checks
  • Implement pub/sub health validation
  • Add email service health checks
  • Create logging system health checks
  • Build centralized health dashboard
  • Implement health-based alerting

📋 JIRA-DEVOPS-006: Implement Automated Rollback with Notifications​

Status: DRAFT - Not Created Description: Create automated rollback system integrated with Intercom for real-time notifications. Currently rollback procedures are manual and inconsistent.

Tasks:

  • Define rollback triggers (failed health checks, elevated error rates)
  • Create rollback automation scripts
  • Integrate with CI/CD pipeline
  • Add Intercom user notifications
  • Test rollback procedures in staging