Pranor Console — Unified Management Dashboard

Version: 1.0.0
Module Path: github.com/vyuvaraj/pranor/console
Default Port: 8083
License: AGPL-3.0 (OSS) / Enterprise License (EE with AI Co-Pilot & Chaos Panel)

Overview

Pranor Console is the unified, premium management dashboard and observability console for the Pranor ecosystem. It provides a single pane of glass for managing all Pranor components — Gate, Pulse, Vault, Mesh, Deploy, Trace, Flow, and more — with a glassmorphic, real-time UI designed for power users. It features global search, chaos engineering controls, incident management, eBPF flamegraphs, and WebSocket-driven live telemetry.

Pranor Console can run as:

• A standalone binary serving the web UI with manual service URL configuration
• An integrated module within the Pranor ecosystem with auto-discovery, mTLS, and federated telemetry

Key Features

Architecture

graph TD

    subgraph UserInterface ["🌐 Glassmorphic Web and TUI Interface"]
        SPA["React / WASM Glassmorphic SPA"]
        TUI["Terminal TUI Control Plane"]
        WSClient["WebSocket Live Telemetry Stream"]
    end

    subgraph BackendCore ["⚡ Central Control Plane Backend"]
        SearchEngine["Global Ecosystem ⌘K Indexer"]
        ChaosControl["Chaos Experiment Orchestrator"]
        IncidentEngine["Incident Triage and Alert Engine"]
        AIAssistant["Autonomous AI Co-Pilot"]
    end

    subgraph ServiceIntegrations ["💾 Platform Services Monitoring Hub"]
        GateSync["Pranor Gate API Sync"]
        PulseSync["Pranor Pulse Queue and DLQ Sync"]
        VaultSync["Pranor Vault Bucket and Vector Sync"]
        TraceSync["Pranor Trace and eBPF Flamegraph Sync"]
    end

    SPA --> SearchEngine
    TUI --> SearchEngine
    WSClient --> SearchEngine
    SearchEngine --> ChaosControl
    SearchEngine --> IncidentEngine
    SearchEngine --> AIAssistant
    AIAssistant --> GateSync
    AIAssistant --> PulseSync
    AIAssistant --> VaultSync
    AIAssistant --> TraceSync

Real-Time WebSocket Telemetry Stream & Global Search Sequence Flow

sequenceDiagram
    autonumber
    participant Admin as Cluster Operator / Web UI
    participant Console as Pranor Console Backend
    participant Gate as Pranor Gate / Pulse / Vault
    participant Trace as Pranor Trace Engine
    participant AI as Autonomous AI Co-Pilot

    Admin->>Console: Open Console Dashboard & Trigger ⌘K Search ("vector-index-01")
    Console->>Console: Index & Match Cross-Module Resources in Memory
    Console-->>Admin: Display Instant Search Matches (<5ms)
    Console->>Gate: Subscribe to Live WebSocket Metrics Stream (/ws/feeds)
    Gate-->>Console: Stream Throughput, Latency & Error Telemetry
    Console->>Trace: Query High-Burn SLO Spans & eBPF Flamegraphs
    Trace-->>Console: Correlated Flamegraph + Span Waterfall
    Console->>AI: Analyze Cluster Anomaly & Suggest Auto-Remediation
    AI-->>Admin: Render Remediation Action Card in Glassmorphic Panel

Ecosystem Cross-Module Integration

Pranor Console provides single-pane-of-glass management for all platform components:

• Pranor Gate: Inspects dynamic HTTP routes, hot-swaps WASM security modules, and monitors AI token costs.
• Pranor Pulse: Browses topics, tracks consumer group partition lag, and performs 1-click DLQ message triage.
• Pranor Vault: Visualizes HNSW vector graph indexes, browses S3 buckets, and manages CoW bucket branches.
• Pranor Trace: Renders interactive eBPF CPU flamegraphs, distributed service dependency maps, and SLO burn rate dashboards.

Installation & Deployment

Binary

cd pranor/console
go build -o pranor-console .
./pranor-console --port 8083

Docker

docker run -p 8083:8083 ghcr.io/vyuvaraj/pranor-console:latest

With Service Discovery

docker run -p 8083:8083 \
  -e PRANOR_CONSOLE_PRANOR_GATE_URL=http://pranor-gate:8080 \
  -e PRANOR_CONSOLE_PRANOR_PULSE_URL=http://pranor-pulse:9090 \
  -e PRANOR_CONSOLE_PRANOR_VAULT_URL=http://pranor-vault:7070 \
  -e PRANOR_CONSOLE_PRANOR_TRACE_URL=http://pranor-trace:8090 \
  -e PRANOR_CONSOLE_PRANOR_MESH_URL=http://pranor-mesh:8089 \
  ghcr.io/vyuvaraj/pranor-console:latest

As Part of Pranor Ecosystem

When running under the Pranor platform, Console auto-discovers all services via Mesh and displays the full topology.

Configuration

Environment Variables

YAML Config (console.yaml)

port: "8083"
gate_url: "http://pranor-gate:8080"
pulse_url: "http://pranor-pulse:9090"
vault_url: "http://pranor-vault:7070"
trace_url: "http://pranor-trace:8090"
mesh_url: "http://pranor-mesh:8089"
auth_token: "admin-secret-token"
theme: "dark"

CLI Flags

API Reference

Base URL: http://localhost:8083

GET /api/v1/search?q=

Global resource search (⌘K).

Response (200):

{
  "results": [
    { "type": "service", "name": "orders-api", "module": "mesh", "url": "/mesh/services/orders-api" },
    { "type": "route", "name": "/api/orders", "module": "gate", "url": "/gate/routes/api-orders" }
  ],
  "took_ms": 3
}

GET /api/v1/topology/graph

Live service topology graph data.

Response (200):

{
  "nodes": [
    { "id": "orders-api", "type": "service", "status": "healthy" },
    { "id": "payments-api", "type": "service", "status": "degraded" }
  ],
  "edges": [
    { "from": "orders-api", "to": "payments-api", "rps": 120, "error_rate": 0.02, "p99_ms": 45 }
  ]
}

POST /api/v1/chaos/experiments

Create a chaos experiment.

Request:

{
  "name": "latency-spike-test",
  "target_service": "payments-api",
  "fault_type": "latency",
  "latency_ms": 500,
  "percentage": 25,
  "duration": "5m"
}

Response (201):

{
  "id": "exp-001",
  "status": "active",
  "blast_radius": ["orders-api", "checkout-api"],
  "expires_at": "2026-08-01T10:05:00Z"
}

POST /api/v1/incidents

Create an incident.

Request:

{
  "title": "High error rate on payments-api",
  "severity": "P2",
  "services": ["payments-api"],
  "description": "Error rate exceeded 5% SLO threshold"
}

Response (201):

{
  "id": "inc-001",
  "status": "open",
  "created_at": "2026-08-01T10:00:00Z"
}

GET /healthz

Liveness probe.

{"status":"UP","service":"pranor-console","version":"1.0.0"}

Security

Standalone Mode

Set PRANOR_CONSOLE_AUTH_TOKEN for basic token authentication. Clients authenticate via:

Authorization: Bearer admin-secret-token

Ecosystem Mode (Full Auth Stack)

When running within the Pranor ecosystem, Console integrates with Pranor Auth for RBAC-based access control:

1. JWT Auth — validates Bearer tokens against Pranor Auth
2. Role-based dashboard access — admins see all panels; operators see limited views
3. Audit logging — all management actions logged with user identity
4. mTLS — service-to-service communication encrypted

CORS

Console serves the SPA from a configurable origin. CORS headers allow the frontend to call backend APIs cross-origin.

Observability

Prometheus Metrics

OpenTelemetry Tracing

Console emits spans for:

• console.search — global search queries
• console.chaos.inject — chaos experiment triggers
• console.topology.refresh — topology graph rebuilds

Logging

Structured JSON logs with fields: level, timestamp, user_id, action, module, latency_ms.

Enterprise Edition

Operational Runbook

WebSocket connections dropping

1. Check pranor_console_active_sessions gauge for sudden drops
2. Verify network stability between Console and downstream services
3. Check if rate limiting is affecting WebSocket upgrade requests
4. Review nginx/load balancer timeout settings for WebSocket connections
5. Ensure Connection: Upgrade headers are not being stripped

Global search returning stale results

1. Console indexes resources on startup and via WebSocket feeds
2. Force re-index by restarting Console or triggering topology refresh
3. Check connectivity to all configured service URLs
4. Verify Mesh is reporting accurate service catalog

Chaos experiment not propagating

1. Verify Pranor Mesh connectivity (PRANOR_CONSOLE_PRANOR_MESH_URL)
2. Check experiment status via GET /api/v1/chaos/experiments/{id}
3. Confirm target service is registered in Mesh service catalog
4. Review blast radius preview before re-triggering

Dashboard panels blank or loading

1. Check browser console for WebSocket connection errors
2. Verify backend service URLs are correct and accessible
3. Check auth token validity if using static token auth
4. Review CORS configuration if frontend is served from a different origin