Log Analysis with Gen AI

Log Analysis with Gen AI. Team Aegis. GenAI.

Implementing a generative AI-powered log analyzer involves feeding log data into models like ChatGPT or Gemini for automated analysis, anomaly detection, and real-time monitoring, while allowing user interaction for specific queries or insights, and continuously optimizing the system based on operational feedback..

Solution. Frequent Incident Tracking: The ServiceNow Log Analyzer diligently monitors both existing and new incidents on a regular basis, ensuring timely response and resolution. Automated Log Analysis: By harnessing Language Model AI (LLM), this system swiftly extracts insights from incident attachments, generating concise summaries that are promptly integrated into work notes. Time-Saving Efficiency: This solution revolutionizes incident management by automating tedious tasks, thereby empowering teams to focus more on strategic initiatives and less on routine operations..

Technologies Used. Python: Used as the primary programming language for backend logic and automation. Requests: Facilitates HTTP requests, including authentication through HTTPBasicAuth. Flask: Provides the framework for building and serving the RESTful API endpoints. Flask-SocketIO: Enables real-time communication through WebSocket protocol. SQLite: Utilized as the relational database management system for data storage and retrieval. GoogleGenerativeAI (LangChain): Integrated for natural language processing and generation capabilities. Threading: Implemented for concurrent execution of tasks to optimize performance..

Key Features. Seamless ServiceNow Integration Advanced Log Analysis with LLM Automatic Work Note Updates Real-time Dashboard Metrics Enhanced Monitoring and Control.

Log Analyzer - Dashboard. Incident Dashboard Total Processed: 79 | Updated Work Notes: 13 | Processing Errors: O Incidents by Priority Incidents by Priority 10 Recent Incidents Incidents by State Incidents by State 25 15 10 Incidents by Category Incidents by Category 50 40 30 20.

Log Analyzer - Dashboard.

Log Analyzer - Dashboard. Log [ 2e24 C 2e24 [2024 [ 2Ø24 [2024 [2024 [2024 [ 2e24 INC0001990 5 INC0008001 5 INC0000002 INC0000006 INC0000008 INCOOOOOOI •42:25] -07-11 [2e24-07-11 •42:25] -07-11 42:26] 42 :26] •43:26] -07-11 [2e24-07-11 •43:26] 43 :26] -07-11 •43.•27] -07-11 [2e24-07-11 •43 : 30] 43 : 30] -07-11 [2e24-07-11 •44:31] 3 1 3 7 7 7 Inquiry inquiry network software inquiry network Unable to access the personal details section in payroll portal ATF:TEST2 Network file shares access issue Hangs when trying to print VISIO document Printer in my office is out of toner Can't read email 2024-07-1 2024-07-1 2024-07-1 2024-07-1 2024-07-1 2024-07-1 -07 -07 14. 14. 14 : 14. 14. 14 : 14. 14. 14 : 14 14. Processing new incident INceeee054 Processing new incident INceeee017 Processing new incident INCeeeeee7 Finished processing. Waiting for 2 minutes before next check... Checking for new incidents... Found 1 incidents to process. Processing new incident INceme013 Found log file: log-file. log Updated work notes for incident INCee1ee13 Finished processing. Waiting for 2 minutes before next check... Checking for new incidents... No new incidents found..

Log Analyzer - Work Notes SNOW LLM Summary. servicenow Incident All Favorites History Incident - INC0010036 Q Search Discuss Follow Update Resolve Post Delete INC0010036 View: self Service Activities: 3 System Administrator Log File Summary (Network Issues.log): Events:" Network monitoring started at 09:00:00. Work notes • 2024-07-11 Network devices DOOI, D002, D003, D004, D005, D006, D007, D008, and D009 were checked and found functioning normally. • Network traffic analyses were completed at and Network segments A1, A2, A3, and A4 experienced high latency and packet loss. "Errors: Packet loss was observed on network segments A1, A2, A3, and A4. • "Important Information:" • Network latency for users 1.11234, U5678, U7890, 1.19012, 1.13456, U6789, U0123, 02345, and U4567 was monitored. • Network segments A1, A2, A3, and A4 were operational after latency issues were resolved. • Network checks were initiated at and.

Vignesh Kalavakuri Siva Vemasani Dhanaraj Marpu – Team Lead Moode Hari Prakash Naik Ponnana Rakesh.

Thank You.