Monitor

Scope

Monitor is an application that can watch site contents, DNS status, and SSL certificate status and detect unexpected changes and alert users when it finds them. It is one of our platform applications and can be found at /a/monitor.

Troubleshooting

Client Error Status 404

If you come across an issue with Client error status (404) as the description it’s caused by the typical reasoning behind a 404 status response. At the time that Monitor did the scan a resource was not found. To resolve this issue the site will need to be fixed by either adding the resource that’s being requested or removing the reference to the resource.

Client error status (404)

Determining where those references to the missing resource are can be done with the following process:

  1. Retrieve the jobId from the Monitor issue url jobId
  2. Stick the retrieved jobId into the following url: https://banno.com/a/monitor/api/jobs/<jobId>/result and then load it up
  3. That should retrieve a big block of json. You’re looking for the bit in the second half of the json where the 404’ed resource is in the url attribute and there’s an accompanying loadedFrom attribute like:
    {
       "url": "https://www.homebankofar.com/img/loading.gif",
       "status": "ok",
       "linkedFrom": [],
       "loadedFrom": [
          "https://www.homebankofar.com/",
          "https://www.homebankofar.com/index.htm"
       ]
    },
    
  4. The urls in the loadedFrom block are the places where the Monitor run found the broken resource