How spatie/laravel-schedule-monitor works
Main Components
a. Core Components:
• Schedule Monitor Service (Central Component)
• Database Storage Layer
• Command Interface Layer
• Oh Dear Integration Service
• Event Handling System
• Task Monitoring Engine
b. External Systems:
• Laravel Application (Host System)
• Oh Dear API Service
• Database System
Component Relationships
[Laravel Application] ←→ [Schedule Monitor Service]
• ↓
[Command Interface] → [Task Monitoring Engine]
• ↓
[Event Handlers] → [Database Storage]
• ↓
[Oh Dear Integration] → [Oh Dear API]
Detailed Component Breakdown
a. Schedule Monitor Service:
• Connection to Models (MonitoredScheduledTask, MonitoredScheduledTaskLogItem)
• Task Factory and Task Types (Command, Job, Shell, Closure)
b. Database Layer:
• Monitored Tasks Table
• Log Items Table
• Task Metadata Storage
c. Command Interface:
• Command
• Sync Command
• Verify Command
d. Oh Dear Integration:
• Payload Factory
• Different Payload Types (Starting, Finished, Failed)
• Queue System for Oh Dear Pings
Data Flow Indicators
• Task Registration Flow
• Monitoring Flow
• Notification Flow
• Logging Flow
Implementation Details
• Service Provider Integration
• Model Relationships
• Event Subscription System
• Queue Management for Oh Dear Notifications