Javascript errors to be ignored

By default, this test alerts administrators to all Javascript errors that occur in the monitored web site/web application. This is why, this parameter is set to none by default. Sometimes however, administrators may not want to be notified when certain types of Javascript errors occur – this could be because such errors are harmless or are a normal occurrence in their environment. In such circumstances, you can instruct the eG agent to ignore these errors when monitoring. For this, specify the Java script error message to be ignored in the JAVASCRIPT errors to be ignored text box, in the following format: <Javascript eror message>:<URL of the page/file where the message originated>.

For instance, say that the login.html page in your web site runs a few Java scripts that throw Object expected errors, which you want the eG agent to ignore. In this case, your error specification can be as follows: Object expected:http://www.eazykart.com/web/login.html. Alternatively, you can provide only that text string with which the error message begins in your specification – eg., Object:http://www.eazykart.com/web/login.html. Moreover, instead of the complete URL, you can specify just the name of the HTML/jsp/aspx page in which the error is to be ignored – example: Object:login.html

Sometimes, the individual web pages in your web site may not run any Java script directly. Instead, these web pages may include links to Java script files that will run the Java script and return the output to the web pages. If you want the eG agent to ignore certain errors thrown by such a Javascript file, then your error pattern specification should include the URL of the Javascript file and not the web page that points to it. This is because, in this case, the file is where the error message originates. For instance, in the same example above, if the login.html page points to a validate.js file, and you want to ignore the Object expected errors that this JS file throws, your error pattern specification will either be, Object expected:validate.js, or Object:validate.js.

Multiple error message-URL combinations can also be provided as a comma-separated list. The format of your specification will be:

<Javascript error message 1>:<Originating URL 1>,<Javascript error message 2>:<Originating URL 2>,. . .

For example, to ignore the Object expected and Uncaught TypeError errors in the login.html page, use the following specification:

Object:login.html,Uncaught:login.html

Likewise, to ignore the Object expected error in the login.html page and the Uncaught TypeError in the validate.js file, your specification will be:

Object:login.html,Uncaught:validate.js

If you want to ignore the Uncaught TypeError across all the pages of the web site, your specification will be as follows:

Uncaught TypeError:All

Note:

When specifying the <Javascript error message> to be ignored, take care of the following:

  • The error message should not contain any special characters – in particular, the ‘:’ (the colon) and the ‘,’ (the comma) characters should be avoided.
  • The case of the actual error message and the one specified as part of your error specification should match. This is because, the eG agent performs case-sensitive pattern matching.