URL WEB MONITORING SERVICES A Project Presented to the faculty of the Department of Computer Science California State University, Sacramento Submitted in partial satisfaction of the requirements for the degree of MASTER OF SCIENCE in Computer Science by Prachi Saxena SPRING 2018 © 2018 Prachi Saxena ALL RIGHTS RESERVED ii URL WEB MONITORING SERVICES A Project by Prachi Saxena Approved by: __________________________________, Committee Chair Dr. Ahmed Salem __________________________________, Second Reader Prof. Haiquan Chen ____________________________ Date iii Student:Prachi Saxena I certify that this student has met the requirements for format contained in the University format manual, and that this project is suitable for shelving in the Library and credit is to be awarded for the project. __________________________, Graduate Coordinator ________________ Dr. Jinsong Ouyang Date Department of Computer Science iv Abstract of URL WEB MONITORING SERVICES by Prachi Saxena With the high increase of Web applications and websites devolvement and usage, monitoring web applications and websites became a necessity to minimize the risk of vulnerability, failures and customer dissatisfaction. The aim of this project is address these issues and develop a centralized service monitoring tool to conduct assessment and collecting relevant Information of the targeted system. This tool is designed to provide more responsive access and cost effective notification to system issues. Furthermore, the tool would allow the creation of alerts by generating report for errors and issues, Monitors overall system status at single source and helps reduces service downtime and improve the overall user experience. The tool services will be provided without SMTP obligations and using Power Shell and AWS (SNS) Web Monitoring Service. ______________________, Committee Chair Dr. Ahmed Salem _______________________ Date v ACKNOWLEGMENT I would like to thank my advisor Dr. Ahmed Salem for guiding me throughout this Project. This project would not appear in its present form without his kind assistance and support. I owe a deep debt of gratitude to my advisor for his belief in my abilities, his enthusiasm for this project, and his continuous insistence that I make it better. He provided encouragement, sound advice, good teaching, and lots of good ideas. I would also like to thank Department of Computer Science at California State University, Sacramento for giving me an opportunity to pursue Masters in Computer Science and guiding me to become a successful student. vi DEDICATION To My Family vii TABLE OF CONTENTS Page Acknowledgments .................................................................................................... vi Dedication ............................................................................................................... vii List of Figures .......................................................................................................... ix Chapter 1. INTRODUCTION ….……….………………………………………………….. 1 1.1. Problem Definition ................................................................................. 1 1.2. Motivation.............................................................................................. 2 1.3. Technologies Used ................................................................................. 2 2. BACKGROUND ............................................................................................... 3 2.1. Ping ....................................................................................................... 3 2.2. Uptime Robot ......................................................................................... 5 2.3. Status Cake ............................................................................................ 6 2.4. App-Dynamics ....................................................................................... 7 3. PROJECT DESIGN ............................................................................................ 8 3.1. Project Architecture .............................................................................. 10 3.1.1. Architecture Components ....................................................... 11 4. PROJECT IMPLEMENTATION...................................................................... 13 4.1. Sample Code ........................................................................................ 13 4.2. Project Execution ................................................................................. 17 4.2.1. Output Report ....................................................................... 18 viii 4.2.2. Output Description Report .................................................... 19 5. MONITORING PROCESS .............................................................................. 20 5.1. Services Description ............................................................................. 21 5.2. Deployment of Services ....................................................................... 23 5.3. Writing A YAML File to Run Services ................................................ 25 5.4. Service Implementation Results............................................................ 32 5.4.1. View Services Status Details for all Host Group .................... 32 5.4.2. Network Health ..................................................................... 33 5.4.3. Network Outage .................................................................... 34 6. CONCLUSION ................................................................................................. 35 References ............................................................................................................... 36 ix LIST OF FIGURES Figures Page 1. Ping…………………………………………………………………………...3 2. Uptime Robot………………………………………………………………...5 3. Status Cake……………………………………………………………….......6 4. App-Dynamics…………………………………………………………….....7 5. Project Architecture………………………………………………………....10 6. Project Execution…………………………………………………………...17 7. Output Report……………………………………………………………….18 8. Host Machines……………………………………………………………....20 9. Services Health Record……………………………………………………..22 10. Status Details for all Host Group…………………………………………...32 11. Network Health Status……………………………………………………...33 12. Network Outage Status……………………………………………………...34 x 1 Chapter 1 INTRODUCTION 1.1.Problem Definition During my summer internship, I have gotten hands-on experience of testing, deploying and monitoring services and application running in a network environment using tools like App-Dynamics, Go-daddy, and many others. These tools are being highly used and recommended in the IT sector. These tools which are efficient and quite successful in reporting the bugs on time and resolving them, but do have room for improvements. The reason that has motivated me to work on this project is a yearning to make a system monitoring experience for organizations or teams to be more qualitative and informative in order to protect the system from abnormality. The tools mentioned above have their own shortcomings; they are open source tools, but that depends on the applications you are running. Secondly, they use pi-charts, histograms, and graphs to depict the status of systems or URLs, which may not be the most desirable way to understand the reasons of failure. In this project, the approach is to provide precise but comprehensive information which can help users and engineers identify issues more easily within a single source and yet a tool that can be stored and managed with minimum memory and low-cost. 2 1.2. Motivation As a software engineer, I have a tendency to find imperfections in every software, application, device or User Interface I use. I always think what existing features can be eradicated or added to make an application more user-friendly, efficient, accurate and human centric. This can provide successful monitoring and deploying of applications and services. In this project, the goal is to work on the shortcomings of already existing commercial tools in terms of efficiency, preciseness, applicability and security. The main motivation is how to make a precise, comprehensive, secure and cost-efficient open source software application in order to serve the purpose of web monitoring. 1.3. Technologies Used ● Power Shell Scripting. ● AWS SNS Services. ● Ansible Software ● Nagios ● HTML ● AWS EC2 instance. 3 Chapter 2 BACKGROUND This section will provide a brief introduction to current applications and will be explain why the proposed solution is important to be practiced. Here, we are going to discuss about Ping, Status Cake, App-Dynamics in details in subsequent sections. 2.1. Ping Figure 1: Ping 4 As shown in Fig. 1, ping is an internet program that allows a user to confirm if a particular IP address exists and accepts requests made by the user on that host. It also has the ability to ensure that a host node that users are trying to reach is actually an operating system. The ping is also known as a software utility to test the availability of a host from a user network. This is a call from the host to identify if another system it is trying to reach is available on the requested network. Ping uses ICMP protocol to send messages or packets from one host to another and also to report any errors. It is essentially a request-response method used by ping. This is an overhead on the processor and it also results in a delayed configuration in case of packet loss. It provides the system uptime status, but it is limited within the network