How ayaanzaroon78/drdo-project works
SecureTelemetry simulates sensor telemetry, validates packets for integrity and sequence errors, records results and security events, then exposes monitoring through REST, WebSockets, and dashboard views. Authentication—including a simulated hardware-key challenge/response flow—is a separate protected workflow. The graph preserves the documented analytics and monitoring capabilities; some subsystem links are based on the README and tree because their implementation was not sampled.
Main entry points: api.ts REST client · packets/services.py Packet ingestion · consumers.py WebSocket consumers · authentication_app/services.py Key challenge service
Components 22
Dashboard client
- Dashboard pages
frontend/app/(dashboard)/dashboard/page.tsx - Feature pages
frontend/app/(dashboard) - REST client
frontend/lib/api.ts - Live socket hook
frontend/hooks/useWebSocket.ts
Telemetry processing
- Sensor simulator
backend/sensors/simulator.py - Sensor API
backend/sensors/views.py - Packet API
backend/packets/views.py - Packet ingestion
backend/packets/services.py - CRC engine
backend/core/crc.py
Authentication
- Authentication API
backend/authentication_app/views.py - Key challenge service
backend/authentication_app/services.py
Monitoring and events
- Analytics API
backend/analytics/views.py - Analytics records
backend/analytics/models.py - Event logger
backend/security_events/services.py - Security event API
backend/security_events/views.py - WebSocket consumers
backend/websocket_app/consumers.py - Socket routing
backend/websocket_app/routing.py
Application state
- Sensor records
backend/sensors/models.py - Packet records
backend/packets/models.py - User and key sessions
backend/authentication_app/models.py - Security events
backend/security_events/models.py
Other components
- Operator
Connections 26
- Operator → Dashboard pages: uses
- Operator → Feature pages: opens
- Dashboard pages → REST client: requests data
- Feature pages → REST client: requests data
- REST client → Sensor API: REST calls
- REST client → Packet API: REST calls
- REST client → Authentication API: REST calls
- REST client → Analytics API: REST calls
- REST client → Security event API: REST calls
- Sensor simulator → Packet ingestion: submits readings
- Sensor API → Sensor records: reads and writes
- Packet API → Packet ingestion: ingests and verifies
- Packet ingestion → CRC engine: calculates CRC
- Packet ingestion → Sensor records: updates sequence
- Packet ingestion → Packet records: stores packets
- Packet ingestion → Event logger: logs failures
- Packet ingestion → WebSocket consumers: broadcasts packets
- Authentication API → Key challenge service: runs key flow
- Key challenge service → User and key sessions: updates sessions
- Key challenge service → Event logger: logs auth events
- Event logger → Security events: stores events
- Security event API → Security events: reads events
- Analytics API → Analytics records: reads metrics
- Socket routing → WebSocket consumers: routes connections
- Live socket hook → WebSocket consumers: receives live packets
- WebSocket consumers → Live socket hook: sends packet updates