How aditya0252/ticket-analysis-tool works
This repository implements network-support ticket analysis, with a broader diagnostic workflow that enriches tickets using customer network data and command recommendations. The ticket API extracts issue details, persists analysis, and supports feedback; the richer app also coordinates vendor-specific lookups, event analysis, and network assessment. Phase 2 provides issue knowledge matching, while Phase 3 provides vendor retrieval and command tooling. Some subsystem links are based on the SOURCE INDEX’s import/reference lists rather than inspected call sites; those lists do not establish exact runtime sequencing.
Main entry points: app_new.py Diagnostic app · ticket_processor.py Ticket processor · command_extractor.py Command extraction · config.py Vendor configuration
Components 24
Ticket analysis
- Ticket API
folder/app.py - Diagnostic app
folder/app_new.py - Ticket processor
folder/ticket_processor.py - Ticket persistence
folder/db_config/db_execute.py - PostgreSQL
- Ticket reply
folder/ticket_reply.py - Zoho integration
folder/zoho_utils.py
Issue knowledge
- Issue data loader
phase2/load_data.py - LLM issue matching
phase2/llm_load_data.py - Use-case splitting
phase2/split_use_cases.py
Network diagnostics
- Network utilities
phase3/utils.py - LinkEye fetch
phase3/linkeye_data_fetch.py - Nautobot connectivity
phase3/nautobot_connectivity.py - Aruba Central data
phase3/aruba_central_info.py - Juniper Mist data
phase3/juniper_mist_data.py - Event analysis
dec_event_analysis.py - Event test bed
dec_test_bed.py - Vendor configuration
phase3/config.py
Vendor retrieval
- Command extraction
phase3/command_extractor.py - Vendor retrieval
phase3/load_embeddings.py - Collection loader
phase3/vendor_loader.py
Other components
- Support user
- LLM service
- Aruba Central
Connections 28
- Support user → Ticket API: submits ticket
folder/app.py - Ticket API → Ticket processor: processes ticket
folder/app.py - Ticket API → Ticket persistence: saves analysis
folder/app.py - Ticket processor → Ticket persistence: persists ticket
folder/ticket_processor.py - Ticket persistence → PostgreSQL: reads and writes
folder/db_config/db_execute.py - Ticket processor → Ticket reply: uses reply logic
folder/ticket_processor.py - Ticket processor → Zoho integration: uses ticket utilities
folder/ticket_processor.py - Diagnostic app → Ticket processor: uses processor
folder/app_new.py - Diagnostic app → Issue data loader: uses issue data
folder/app_new.py - Issue data loader → LLM issue matching: imports matching
phase2/load_data.py - LLM issue matching → LLM service: requests matches
phase2/llm_load_data.py - Diagnostic app → Network utilities: uses utilities
folder/app_new.py - Diagnostic app → LinkEye fetch: uses LinkEye data
folder/app_new.py - Diagnostic app → Nautobot connectivity: uses connectivity
folder/app_new.py - Diagnostic app → Aruba Central data: uses Aruba data
folder/app_new.py - Diagnostic app → Juniper Mist data: uses Mist data
folder/app_new.py - Diagnostic app → Event analysis: uses event analysis
folder/app_new.py - Event analysis → Event test bed: imports event tools
dec_event_analysis.py - Diagnostic app → Command extraction: uses commands
folder/app_new.py - Command extraction → Network utilities: imports utilities
phase3/command_extractor.py - Command extraction → Vendor retrieval: retrieves context
phase3/command_extractor.py - Command extraction → Collection loader: uses collections
phase3/command_extractor.py - Vendor retrieval → Collection loader: loads collections
phase3/load_embeddings.py - Aruba Central data → Vendor configuration: imports settings
phase3/aruba_central_info.py - Juniper Mist data → Vendor configuration: imports settings
phase3/juniper_mist_data.py - Nautobot connectivity → Vendor configuration: imports settings
phase3/nautobot_connectivity.py - LinkEye fetch → Vendor configuration: imports settings
phase3/linkeye_data_fetch.py - Aruba Central data → Aruba Central: calls API
phase3/aruba_central_info.py