PR-Tracker can be used to collect exception data from application programs that are either in internal to your company or installed in the field by your customers. The diagram below shows a PR-Tracker deployment that includes the PR-Tracker Exception Management Service. When an exception occurs in an application, it can be sent by the application to PR-Tracker over an intranet or the Internet.
When an exception is received by the PR-Tracker Exception Management Service, it will create a problem report for the exception provided that it is the first time the exception has occurred. If the exception has occurred before, an occurrence count will be incremented instead. The occurrence count can help you determine which exceptions are affecting the user experience the most and help you to prioritize which exceptions to fix first.
The transmitted exception data includes the following information to help you debug the exception: the call stack, user actions (such as a button or menu click), trace information, configuration settings and the version of the application.
In some cases, an exception may be fixed in an updated version of software. In other cases there may be actions which the user should perform to eliminate the exception. This information can be entered into the exception’s problem report and it will be sent back to the application program as a response.
To implement a system such as the one depicted above you have to do these things:
See also Using An Exception Collector Project