feat(backend): Add MCP client activity metrics cleanup job and worker

Author: Lasim

README.md

@@ -148,6 +148,7 @@ VS Code → HTTPS Request → DeployStack Satellite → MCP Server Process → E
 - **[Done]** **Resource Management** - process isolation (remote MCP) and limits
 - **[Done]** **GitHub README and Stars Integration** - automatic GitHub data fetching, secure storage, XSS prevention, DoS protection, and comprehensive audit logging for MCP server catalog enhancement
 - **[Done]** **Background Job Queue System** - complete 4-phase custom SQLite-based job queue with worker infrastructure, admin API, frontend monitoring UI, and comprehensive documentation for long-running tasks
+- **[Done]** **Cron Job Scheduling System** - recurring task scheduler using node-cron with integration into the job queue system, standard cron expression support, automatic lifecycle management, and complete separation of scheduling logic from execution for reliability and monitoring
 - **[Done]** **Frontend Syntax Highlighting** - reusable CodeHighlight component with Prism.js for JSON, JavaScript, TypeScript, Bash, and YAML code blocks
 - **[Done]** **Resource Management** - process isolation (stdio) and limits
 - **[Done]** **MCP Registry** - integration of the official MCP Registry
@@ -164,6 +165,7 @@ VS Code → HTTPS Request → DeployStack Satellite → MCP Server Process → E
 - **[Done]** **Satellite Job System** - recurring background task management with JobManager, abstract BaseJob class, automatic error handling, execution metrics tracking, and extensible architecture for health checks, cleanup tasks, and periodic maintenance operations
 - **[Done]** **Satellite Backend Events System** - real-time event processing with convention-based auto-discovery handler pattern, batch processing (1-100 events), partial success handling, JSON schema validation per event type, and extensible architecture supporting MCP client connections, tool executions, server crashes, and custom event types
 - **[Done]** **MCP Client Activity Tracking** - personal dashboard feature tracking active MCP clients per user across all components (backend database with mcpClientActivity table, satellite in-memory tracker with 30-second background job reporting via event system, dashboard API endpoint with dual authentication and pagination, client name detection from OAuth/headers/user-agent)
+- **[Done]** **Time-Series Metrics System** - production-ready metrics infrastructure with 15-minute bucket aggregation, 3-day retention, automated cleanup
 - **[To Do]** **Comprehensive Monitoring** - satellite health and usage analytics
 - **[To Do]** **Enterprise Security** - audit logging and compliance features
 

services/backend/README.md

@@ -91,8 +91,7 @@ npm run start
 npm run lint
 
 # Database migrations
-npm run db:generate  # Generate new migrations
-npm run db:up        # Apply migrations
+npm run db:generate  # Generate new migrations (applied automatically on server startup)
 
 # API documentation
 npm run api:spec      # Generate OpenAPI spec

services/backend/api-spec.json

@@ -5203,27 +5203,25 @@
                 "6h",
                 "12h",
                 "24h",
-                "7d",
-                "30d"
+                "3d"
               ]
             },
             "in": "query",
             "name": "time_range",
             "required": false,
-            "description": "Time range for metrics (e.g., 3h, 24h, 7d)"
+            "description": "Time range for metrics (maximum 3 days for MCP client activity)"
           },
           {
             "schema": {
               "type": "string",
               "enum": [
-                "15m",
-                "1h"
+                "15m"
               ]
             },
             "in": "query",
             "name": "interval",
             "required": false,
-            "description": "Bucket interval for aggregation"
+            "description": "Bucket interval for aggregation (only 15m supported for MCP client activity)"
           },
           {
             "schema": {

services/backend/api-spec.yaml

@@ -3590,21 +3590,20 @@ paths:
               - 6h
               - 12h
               - 24h
-              - 7d
-              - 30d
+              - 3d
           in: query
           name: time_range
           required: false
-          description: Time range for metrics (e.g., 3h, 24h, 7d)
+          description: Time range for metrics (maximum 3 days for MCP client activity)
         - schema:
             type: string
             enum:
               - 15m
-              - 1h
           in: query
           name: interval
           required: false
-          description: Bucket interval for aggregation
+          description: Bucket interval for aggregation (only 15m supported for MCP client
+            activity)
         - schema:
             type: string
           in: query

services/backend/drizzle/migrations_sqlite/0009_naive_tigra.sql

@@ -0,0 +1,2 @@
+DROP INDEX `mcp_activity_metrics_unique_bucket`;--> statement-breakpoint
+CREATE UNIQUE INDEX `mcp_activity_metrics_unique_bucket` ON `mcpClientActivityMetrics` (`user_id`,`team_id`,`satellite_id`,`auth_identifier`,`bucket_timestamp`,`bucket_interval`);