How palisadoesfoundation/switchmap-ng works
Main Components Identification
a) Poller Service (/switchmap/poller/)
• SNMP polling functionality
• MIB handling for different vendors (Cisco, Juniper, Generic)
• Device data collection
b) Server Component (/switchmap/server/)
• Database management
• API endpoints
• Data ingestion system
c) Dashboard (/switchmap/dashboard/)
• Web interface
• Data visualization
• Search functionality
• Device monitoring
d) Database Layer (/switchmap/server/db/)
• Multiple tables (device, event, IP, MAC, VLAN, etc.)
• Data models and schemas
[Network Devices]
• ↓ SNMP
[Poller Service] → [Server Component] ← [Dashboard]
• ↓ ↕ ↑
• [Database Layer] [Web Browser]
Component Details
For each component, include these specific elements:
Poller Service:
• SNMP Manager
• MIB Handlers (Cisco, Juniper, Generic)
• Device Update System
Server Component:
• GraphQL API
• REST Endpoints
• Data Ingest Pipeline
• Database Connectors
Dashboard:
• HTML Templates
• Device Pages
• Search Interface
• Event Monitoring
Database Layer:
• Device Tables
• MAC/IP Tables
• VLAN Tables
• Event Logging
Data Flow Indicators
• SNMP polling flow from devices
• Data ingestion path
• API requests/responses
• User interface interactions
Integration Points
Highlight:
• API endpoints
• Database connections
• SNMP communication channels
• Web server interfaces
Additional Elements
Include:
• Version information
• System requirements
• Key dependencies
Technical Details
Specifications:
• Python-based implementation
• SNMP protocol usage
• Web framework details
• Database technology
Deployment Context
Show:
• System boundaries
• External dependencies
• Network boundaries
• Security zones
Remember to include notes about:
• Scalability considerations
• Security boundaries
• Data flow directions
• Component dependencies
This will provide a clear understanding of how Switchmap-NG operates as a complete system for monitoring and visualizing Ethernet switch information.