Website Monitoring

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
User avatar
emartine
Posts: 660
Joined: Thu Dec 29, 2011 10:47 am

Website Monitoring

Post by emartine »

I was asked to search for a string on a web page to ensure that the page is available so I used the web monitoring wizard only to find it fail because the page requires java script. The index.html file gives a generic message.

JavaScript is either disabled in or not supported by the Web browser.
To continue logon, use a Web browser that supports JavaScript or enable JavaScript in your current browser.

Although I can probably monitor this, it wouldn't be monitoring what a user would experience should the main page go down.

Is there any way to monitor the content of a web page that requires javascript?
User avatar
cdienger
Support Tech
Posts: 5045
Joined: Tue Feb 07, 2017 11:26 am

Re: Website Monitoring

Post by cdienger »

I'm not aware of anything that will process javascript, but are you seeing this message when you view the source of the index.html or is this just what is seen when you point your browser to it? Sometimes these messages are will display if javascript can't run but the source will show the javascript that was intended to run.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
User avatar
emartine
Posts: 660
Joined: Thu Dec 29, 2011 10:47 am

Re: Website Monitoring

Post by emartine »

I did a wget against the url and the index file is what comes up.
User avatar
mcapra
Posts: 3739
Joined: Thu May 05, 2016 3:54 pm

Re: Website Monitoring

Post by mcapra »

emartine wrote:I did a wget against the url and the index file is what comes up.
As in the index file with the fully rendered content you expect, or the index file with the "Javascript errors", or the un-rendered raw HTML with no Javascript evals?

My hunch is this has to do with the page you're retrieving requiring you to set/provide cookies before fully loading the content. check_http and cURL aren't very good at doing that in a single step.

There's probably things you can do to trick the page into accepting a check_http or cURL request, but without knowing more about the underlying Javascript supporting this website I'd have no idea where to start.

You could try something like CasperJS, Selenium, or the Web Transaction wizard (which uses WebInject).
Former Nagios employee
https://www.mcapra.com/
User avatar
cdienger
Support Tech
Posts: 5045
Joined: Tue Feb 07, 2017 11:26 am

Re: Website Monitoring

Post by cdienger »

Thanks for the input, @mcapra.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
User avatar
emartine
Posts: 660
Joined: Thu Dec 29, 2011 10:47 am

Re: Website Monitoring

Post by emartine »

Please close this. I'll use another tool for monitoring the site. Thank you.
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Website Monitoring

Post by scottwilkerson »

emartine wrote:Please close this. I'll use another tool for monitoring the site. Thank you.
Locking
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
Locked