feat: Implement runner execution pipeline with planner dispatch and execution services
	
		
			
	
		
	
	
		
	
		
			Some checks failed
		
		
	
	
		
			
				
	
				Docs CI / lint-and-preview (push) Has been cancelled
				
			
		
		
	
	
				
					
				
			
		
			Some checks failed
		
		
	
	Docs CI / lint-and-preview (push) Has been cancelled
				
			- Introduced RunnerBackgroundService to handle execution of runner segments. - Added RunnerExecutionService for processing segments and aggregating results. - Implemented PlannerQueueDispatchService to manage dispatching of planner messages. - Created PlannerQueueDispatcherBackgroundService for leasing and processing planner queue messages. - Developed ScannerReportClient for interacting with the scanner service. - Enhanced observability with SchedulerWorkerMetrics for tracking planner and runner performance. - Added comprehensive documentation for the new runner execution pipeline and observability metrics. - Implemented event emission for rescan activity and scanner report readiness.
This commit is contained in:
		| @@ -161,6 +161,7 @@ Provision the following secrets/configs (names can be overridden via Helm values | ||||
| - [ ] Tempo and Loki report tenant activity (`/api/status`). | ||||
| - [ ] Retention policy tested by uploading sample data and verifying expiry. | ||||
| - [ ] Alerts wired into SLO evaluator (DEVOPS-OBS-51-001). | ||||
| - [ ] Component rule packs imported (e.g. `docs/ops/scheduler-worker-prometheus-rules.yaml`). | ||||
|  | ||||
| --- | ||||
|  | ||||
|   | ||||
		Reference in New Issue
	
	Block a user