Overview¶

subscribed/incident-monitor has two responsibilities:

• Create and de-duplicate tickets in external systems
• Run resumable health checks in WordPress and emit incidents

Goals¶

• Create tickets in external systems through pluggable connectors
• Support per-request project targeting
• Support optional assignee, tags, and due date
• Prevent duplicate ticket creation with fast local de-duplication
• Run sliced health checks with persisted state and retry handling

Package areas¶

• Subscribed\IncidentMonitor\... The core ticketing layer
• Subscribed\IncidentMonitor\HealthCheck\... The WordPress health check runner

Entry points¶

• Ticketing bootstrap: Subscribed\IncidentMonitor\Container\IncidentMonitorBootstrap
• Facade: Subscribed\IncidentMonitor\Facade\IncidentMonitorFacade
• Health check bootstrap: Subscribed\IncidentMonitor\HealthCheck\Bootstrap
• Package helper: bootstrap.php

Documentation map¶

• Ticket Tracking
• Health Checks
• Async Queue
• Migrations