A web application can encounter a variety of problems. Most of them are handled by the default system error-detection rules in BMC Real End User Experience Monitoring. However, you can extend this capability with up to 100 custom error-detection rules that reflect specific needs of your web application.
Message types
Message type | Typical use case | Resolution |
---|---|---|
Application-specific errors | Many application environments have their own error pages that handle problems gracefully. | There is two ways to detect this error:
|
Built-in errors | You might only care about a 404 Page Not Found error only if it affects a container or a document but not a component of a page. | Turn off the system default "not found" error-detection rule and replace it with a more detailed one that looks for "not found" errors on certain types of objects. |
Subjective or performance errors | If a PDF file takes more than 2 minutes to download, you might consider this a problem. | Create a custom rule that is triggered when objects ending with .pdf have an end-to-end time longer than 2 minutes. |
Interesting events in your web traffic | You might consider a particular user's logging on to be important. | Define an error-detection rule that contains an informational condition to watch for this. |
In the Administration > Thresholds and problem detection > Error detection rules page of a Real User Analyzer, you can perform the following operations:
Creating a custom error-detection rule
Configuring error alert notifications