Site Monitoring Application

We are to create a Site Healthcheck application. The first step of the process is to present the user with an input form HealthCheck Form Definition Job Name Textbox for a list of sitemaps. e.g. [login to view URL] Testbox for a list of simple URLs to check. e.g. [login to view URL] , [login to view URL] Adsense ID Links to check per sitemap (Default: 10) We want to perform 3 simple checks for each page Health Criteria 1. Does the page exist? Did we get a standard HTTP response from the server? 2. Download time. How many seconds does it take to download the page? If a page takes longer than 15 seconds to download, this criterion fails. 3. Adsense ID. This criterion passes if the Adsense ID in the page source matches the expected Adsense ID entered in the form. Process 1 - Run a site health check based on user input 1. The user goes to the health check page, and is presented with the health check form. 2. When the user hits submit, save the input parameters from the input form to a job definition file. This definition file stores all the parameters that the user set in step 1. 3. Determine which pages need to be checked. This includes all simple (non site-map) URLs, and a fixed number of links from each sitemap, randomly selected. 4. Check each URL in turn. Output the URL along with a success/fail message. This data should be flushed to the users browser 5. At the end of the healthcheck process, output a summary to the user. The summary should be in following format: passed failed [login to view URL] s1-p s1-f [login to view URL] s2-p s2-f s1-p and s1-f represent the number of pages that pass or fail, respectively. The user should be able to click on the fail number, and look at the list of URLs that have failed. Process 2 - Run a site health check based on a job name Basically the same as process 1, except that the user will pass the name of a job to the process as part of the querystring. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). * * *This broadcast message was sent to all bidders on Wednesday Dec 20, 2006 7:29:01 AM: I have now updated the specification and responded to all comments. The main changes to the spec include dropping the php error check (too hard), and adding new "run job from a querystring" functionality, so the process can be run from a cron job on a regular basis. The max bid has also been raised. Let me know if you have any further questions. ## Platform To be written in PHP 4