git.stella-ops.org/docs/features/unchecked/web/signals-runtime-dashboard.md

Signals & Runtime Dashboard

Module

Web

Status

IMPLEMENTED

Description

eBPF/ETW/dyld probe status monitoring, signal collection metrics, anomaly alerts, host coverage map, and real-time event stream. API client and models exist but dedicated feature UI module not found as standalone directory.

What's Implemented

• Existing components:
  • extension-slot (src/Web/StellaOps.Web/src/app/core/plugins/extension-slots/extension-slot.component.ts)
• Existing services:
  • evidence-panel-metrics (src/Web/StellaOps.Web/src/app/core/analytics/evidence-panel-metrics.service.ts)
  • gateway-metrics (src/Web/StellaOps.Web/src/app/core/api/gateway-metrics.service.ts)
  • policy-interop (src/Web/StellaOps.Web/src/app/core/api/policy-interop.service.ts)
  • reachability-integration (src/Web/StellaOps.Web/src/app/core/api/reachability-integration.service.ts)
  • vuln-export-orchestrator (src/Web/StellaOps.Web/src/app/core/api/vuln-export-orchestrator.service.ts)

What's Missing

• Signals dashboard feature module: No src/Web/StellaOps.Web/src/app/features/signals/ directory with dedicated dashboard components
• Probe status monitoring: No component showing eBPF/ETW/dyld probe health status per host
• Signal collection metrics: No real-time metrics showing signals collected per second, error rates, latency
• Anomaly alerts panel: No panel displaying detected anomalies from signal data
• Host coverage map: No visualization showing which hosts have active runtime probes
• Real-time event stream: No WebSocket/SSE-based live event feed component

Implementation Plan

• Create features/signals/ module with route registration
• Build probe status monitoring dashboard showing per-host probe health
• Add signal collection metrics widget with real-time updates
• Build anomaly alerts panel consuming anomaly events from Signals backend
• Create host coverage map visualization
• Add WebSocket/SSE integration for real-time event streaming

E2E Test Plan

• Setup:
  • Log in with a user that has appropriate permissions
  • Navigate to the relevant page/section where this feature appears
  • Ensure test data exists (scanned artifacts, SBOM data, or seed data as needed)
• Core verification:
  • Verify the dashboard loads without errors and displays summary cards/metrics
  • Verify data refreshes correctly and loading states are shown
  • Verify empty state is displayed when no data is available
• Edge cases:
  • Verify graceful handling when backend API is unavailable (error state)
  • Verify responsive layout at different viewport sizes
  • Verify accessibility (keyboard navigation, screen reader labels, ARIA attributes)