Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Website login Monitor

Hi There,

I want to do a monitoring of website without associating it to any node that is currently being monitored. Basically, I want to go to a url-> fill the credentials and check whether the login is happening and also check for markers in the web page just to confirm whether is website is loading as intended. Have check HTTP login form monitor and Web Link Monitor and it does to seems to suite my need. These to needs to be associated to a node that is being monitored...but the thing is that these nodes run more than one websites.

Thanks

Find more posts tagged with

website

webpage_monitor

Accepted answers

bobross

You can create one 'External Node' and attach multiple HTTP monitors. The IP of the HTTP monitor does not need to match the IP of the node being monitored. HTTP Monitors don't allow for dynamic login. You could work your way through it with a custom script, but you should also look into SEUM as this might be more beneficial for you.

We've run into a few websites where a standard HTTP Monitor isn't sufficient for verifying that the page is functional and have begun implementing SEUM for these sites. So far SEUM seems pretty powerful and gives us the ability to actually mimic the user experience.

All comments

bobross

Shailesh1

Any idea what the error "Failed to deserialize probe setting....The remote server returned an error: (406) Not Acceptable. As per the attached screen print? My url is correct (I have erased the url from screen print) and all the keywords are correct.

Thanks.

aLTeReGo

Here's a brief description of the 406 error that was returned by the server.

The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

Unless it was a HEAD request, the response SHOULD include an entity containing a list of available entity characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice MAY be performed automatically. However, this specification does not define any standard for such automatic selection.

      Note: HTTP/1.1 servers are allowed to return responses which are      not acceptable according to the accept headers sent in the      request. In some cases, this may even be preferable to sending a      406 response. User agents are encouraged to inspect the headers of      an incoming response to determine if it is acceptable.

If the response could be unacceptable, a user agent SHOULD temporarily stop receipt of more data and query the user for a decision on further actions.

Is it at all possible that the URL being tested includes javascript as part of the form data, redirects, requires a valid acceptable HTTP referrer, or relies on host header information? The HTTP Form Login component monitor included in APM is not very sophisticated and has known limitations with several of these technologies. Most common issues are related to javascript forms and servers that rely on HTTP Host Header information. In these scenarios I would recommend looking at our Synthetic End User Monitor solution that does not suffer from any of these shortcomings.

Shailesh1

Apparently I checked the source of the login page and could find the below codes:

 <form id="form" method="POST" action="">https://XXXXX&quot; onsubmit="        var ok = true;        var email = document.getElementById('email');        var psw = document.getElementById('psw');        var checkbox = document.getElementById('check');        msg('');        if (email.value == '') {          var missingEmailError = document.getElementById('missingEmailError');          email.focus();          msg(missingEmailError.innerHTML);          ok = false;        }        return ok;

Seems that it is using javascript.