Used Python and Selenium to automate DNS and Authentication server monitoring

1. Automated Monitoring Systems
Akshay Aravindan | Palo Alto
Akshay Aravindan
IT Department
akshaya@vmware.com
(510) 366 8442
Sergey Grigoryev Joe Lazzeroni
Anish Kumar Will Stokes
Chris Hopkins Benjamin Guzman
Lakshmisha K P Shalini Gupta
Acknowledgements
1. Current System
2. Importance
500 DNS and Authentication servers
400,000Requests fail hourly
Background
3. Benefits of Automation
4. Program Flow
Solution
5. Current vs Proposed System
Current System – Reactive:
After a problem is brought up, a solution
is put in place
Proposed System – Proactive:
Before a problem is brought up, a
solution is put in place
6. Reduce Failures, Reduce
Downtime
7. Future Development
- Use real-time data
- Integrate HelpNow tickets
- Allow site-specific searches
- Changeable filters through portal
Benefits
Ticket is
Opened
•Faulty DNS or
Authentication
system reported
IT
Department
•Ticket passed to
appropriate team
Root Cause
Analysis
•Problem with DNS
or Authentication
server identified
Ticket is
Closed
•Issue is fixed
Manual Automated
Separate 500 Servers 15 Hours <1 Second
Test Critical Servers 30 Hours 5 Minutes
Solve Problem / Notify Owner 1 Hour 3 Minutes
Updating Web Portal 2 Hours <1 Second
Total 48 Hours = 6 Days 8 Minutes
DNS
Monitoring
•Detect
Malware
•Detect DDOS
Attacks
Authentication
Monitoring
•Detect
security
breaches
Contact