SignalR Real-time Updates - AIUsagePlatform API Portal

📋 Implementation Status

SignalR real-time updates are planned but not yet implemented. Current dashboard updates require page refresh or polling. This document outlines the proposed architecture for live updates.

✗ Not Implemented ⚠ Planned Q3 2026 High Priority

Architecture Event Types Security ← Redis Caching → Background Jobs

🏗️ Proposed SignalR Architecture

SignalR Real-time Architecture (Proposed) ═══════════════════════════════════════════════════════════════════════════════ ┌─────────────────────────────────────────────────────────────────────────────┐ │ CURRENT STATE (Polling) │ ├─────────────────────────────────────────────────────────────────────────────┤ │ │ │ Angular Dashboard API Database │ │ │ │ │ │ │ │ GET /dashboard │ │ │ │ │────────────────►│ │ │ │ │ │ SELECT... │ │ │ │ │───────────────────────►│ │ │ │ │◄───────────────────────│ │ │ │◄─────────────────│ │ │ │ │ │ │ │ │ │ (Wait 30s) │ │ │ │ │ │ │ │ │ │ GET /dashboard │ │ │ │ │────────────────►│ │ │ │ │ ...repeat... │ │ │ │ │ │ ⚠ Problems: │ │ • Wasted resources (constant polling) │ │ • Delayed updates (30s polling interval) │ │ • Server load (N clients × M requests) │ │ │ └─────────────────────────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────────────────────────┐ │ PROPOSED STATE (SignalR) │ ├─────────────────────────────────────────────────────────────────────────────┤ │ │ │ ┌──────────────┐ ┌──────────────┐ ┌───────────┐ │ │ │ Agent │ │ SignalR Hub │ │ Redis │ │ │ │ (Tray) │ │ (Backplane) │ │ (Pub/Sub)│ │ │ └──────┬───────┘ └──────┬───────┘ └─────┬─────┘ │ │ │ │ │ │ │ │ Session Events │ │ │ │ │ (AI detected) │ │ │ │ │──────────────────────────────►│ │ │ │ │ │ │ │ │ │ │ Broadcast to Group │ │ │ │ │ (OrganizationId) │ │ │ │ │───────────────────────────►│ │ │ │ │ │ │ │ │ │◄───────────────────────────│ │ │ │ │ │ │ │ ┌──────┴───────┐ ┌──────┴───────┐ ┌─────┴─────┐ │ │ │ Angular │ │ API Server │ │ Database │ │ │ │ Dashboard │◄─────────────│ (Hub Host) │ │ │ │ │ │ │ WebSocket │ │ │ │ │ │ └──────────────┘ └──────────────┘ └───────────┘ │ │ │ │ Hub Groups (Tenant Isolation): │ │ • group:org-123 → Users in organization 123 │ │ • group:admin → All admin users │ │ • group:superadmin → SuperAdmin only │ │ │ │ Benefits: │ │ • Instant updates (WebSocket push) │ │ • Reduced server load (persistent connections) │ │ • Scalable with Redis backplane │ │ • Bidirectional communication (notifications, alerts) │ │ │ └─────────────────────────────────────────────────────────────────────────────┘

📡 Real-time Event Types

Event	Source	Target Group	Payload	Use Case
`SessionStarted`	Agent	org:{orgId}	{ sessionId, userId, startTime }	Live activity feed
`SessionEnded`	Agent	org:{orgId}	{ sessionId, duration, aiUsageTime }	Real-time dashboard KPI update
`AIDetected`	Agent	org:{orgId}	{ tool, duration, userId }	AI usage tracking
`DashboardUpdate`	Backend	org:{orgId}	{ metrics, trends }	Aggregated dashboard refresh
`ExportCompleted`	ExportJob	user:{userId}	{ jobId, downloadUrl }	Export ready notification
`Alert`	System	org:{orgId} or user:{userId}	{ type, message, severity }	System notifications
`UserJoined`	Auth	org:{orgId}	{ userId, email, timestamp }	Activity monitoring

🔐 Security Model

SignalR Authentication & Authorization ═══════════════════════════════════════════════════════════════════════════════ WebSocket Connection Establishment: ─────────────────────────────────────────────────────────────────────────────── 1. Client Requests Connection Upgrade GET /hubs/analytics?access_token=eyJhbG... Headers: • Authorization: Bearer {JWT} • X-Organization-Id: org-123 │ ▼ 2. Server Validates JWT ┌─────────────────────────────────────┐ │ • Verify signature (RS256) │ │ • Check expiration │ │ • Extract claims: │ │ - sub (UserId) │ │ - org (OrganizationId) │ │ - role │ └─────────────────────────────────────┘ │ ▼ 3. Authorize Hub Connection ┌─────────────────────────────────────┐ │ [Authorize(Roles = "Admin,Manager")]│ │ │ │ • Check role claim │ │ • Verify org matches request │ │ • Validate subscription status │ └─────────────────────────────────────┘ │ ▼ 4. Add to Tenant Group ┌─────────────────────────────────────┐ │ await Groups.AddToGroupAsync( │ │ Context.ConnectionId, │ │ $"org:{orgId}"); │ │ │ │ // User now receives all events │ │ // broadcast to org:{orgId} │ └─────────────────────────────────────┘ 5. Connection Established WebSocket UPGRADE 101 Switching Protocols Tenant Isolation in SignalR: ─────────────────────────────────────────────────────────────────────────────── • Each user joins group: "org:{theirOrganizationId}" • Hub methods verify Context.User belongs to target org • SuperAdmins can join multiple groups or "superadmin" group • Messages filtered server-side before broadcast

⚙️ Implementation Components

1. AnalyticsHub (Server)

public class AnalyticsHub : Hub
{
    [Authorize]
    public async Task JoinOrganizationGroup()
    {
        var orgId = Context.User.GetOrgId();
        await Groups.AddToGroupAsync(
            Context.ConnectionId, $"org:{orgId}");
    }

    public async Task BroadcastDashboardUpdate(
        string orgId, DashboardMetrics metrics)
    {
        await Clients.Group($"org:{orgId}")
            .SendAsync("DashboardUpdate", metrics);
    }
}
                

2. Angular Service (Client)

@Injectable()
export class RealtimeService {
  private hubConnection: HubConnection;

  connect() {
    this.hubConnection = new HubConnectionBuilder()
      .withUrl('/hubs/analytics', {
        accessTokenFactory: () => this.getJwtToken()
      })
      .build();

    this.hubConnection.on('DashboardUpdate', 
      (metrics) => this.updateDashboard(metrics));

    return this.hubConnection.start();
  }
}
                

3. Event Publisher

public class SessionEventPublisher
{
    private readonly IHubContext _hub;

    public async Task PublishSessionStarted(
        Session session)
    {
        await _hub.Clients
            .Group($"org:{session.OrganizationId}")
            .SendAsync("SessionStarted", new {
                session.Id,
                session.UserId,
                session.StartTime
            });
    }
}
                

4. Redis Backplane

// Program.cs
builder.Services.AddSignalR()
    .AddStackExchangeRedis("connectionString", 
        options => {
            options.Configuration.ChannelPrefix = 
                "AIUsagePlatform";
        });

// Enables multiple API servers to share connections
                

📊 Scaling Architecture

SignalR Scaling with Redis Backplane ═══════════════════════════════════════════════════════════════════════════════ ┌─────────────────────────────────────────────────────────────────────────────┐ │ MULTIPLE API SERVERS │ ├─────────────────────────────────────────────────────────────────────────────┤ │ │ │ ┌─────────────────┐ ┌──────────────┐ ┌─────────────────┐ │ │ │ API Server 1 │ │ Redis │ │ API Server 2 │ │ │ │ (SignalR) │◄────►│ Backplane │◄──────►│ (SignalR) │ │ │ │ │ │ │ │ │ │ │ │ • Connections │ │ • Pub/Sub │ │ • Connections │ │ │ │ • Hub instances │ │ • Scale-out │ │ • Hub instances │ │ │ └────────┬────────┘ └──────────────┘ └────────┬────────┘ │ │ │ │ │ │ │ WebSocket connections │ │ │ ▼ ▼ │ │ ┌─────────────────┐ ┌─────────────────┐ │ │ │ Angular │ │ Angular │ │ │ │ Client A │ │ Client B │ │ │ └─────────────────┘ └─────────────────┘ │ │ │ │ When Server 1 broadcasts to group "org:123": │ │ 1. Server 1 publishes to Redis channel "org:123" │ │ 2. Redis forwards to Server 2 │ │ 3. Server 2 delivers to its connected clients in org:123 │ │ │ │ Result: Client B receives message even though connected to Server 2 │ │ │ └─────────────────────────────────────────────────────────────────────────────┘

⚠️ Implementation Risks

⚠

Connection Limits

IIS/Web server has concurrent connection limits. May need dedicated SignalR service or Azure SignalR Service.

⚠

Memory Usage

Each WebSocket connection consumes memory. 10K concurrent connections = significant RAM usage.

⚠

Proxy/WebSocket Support

Corporate proxies may block WebSockets. Need fallback to Server-Sent Events or Long Polling.

✅ Implementation Checklist

Phase 1: Infrastructure

□ Add SignalR NuGet package
□ Configure Redis backplane
□ Setup WebSocket support in IIS
□ Configure CORS for WebSocket

Phase 2: Hub Implementation

□ Create AnalyticsHub class
□ Implement authentication
□ Add tenant group management
□ Create event publisher service

Phase 3: Frontend

□ Add SignalR client library
□ Create RealtimeService
□ Subscribe to dashboard events
□ Handle reconnection logic

Phase 4: Integration

□ Hook session events to SignalR
□ Hook export completion events
□ Add notification system
□ Load testing (10K+ connections)