In the example a test application is used. This application consists of a Windows application (SomeWindowApplication) that calls a web service (SomeWebService). When the web service is called an exception is thrown. Both the Windows application and the web service log the error as a fatal error.

If you would like to test the example, the test application can be downloaded here. The test application is located in a .NET 2.0 solution that also contains other examples.

The test application logs in the online UptoLog Log Server for testing. The logs can subsequently be seen through the online UptoLog Search Server for testing. Where you can try the search options in UptoLog Search Server and view how the logs are visualized.
If you want the test application to log in your own UptoLog Log Server the UptoLog Log Server URL in all config files must be changed to point at your own server. Further information can be found in integrate UptoLog Satellite.

The application failure visualized

The logs are gathered in UptoLog Database which makes it easy for UptoLog Search Server to search across all logs.
Initially the log from the Windows application is found after which the activity connection to the log from the webservice is found. Finally the detailed fatal error logs are studied.

Here the latest fatal error log from the Windows application (SomeWindowsApplication) is found by searching for product name.
As can be seen the activity contains 2 fatal error logs. To view all logs of the activity click the link This activity

Here the activity correlation is shown for the application failure in question with two fatal error logs, one from the Windows application and one from the web service.
To see the details of each log, the log’s heading is clicked.

Here the details of the logging of the error’s source in the web service are shown. As can be seen a DivideByZeroException was thrown and information about where the error occurred is shown. Further information can be found under Additional details.

Here the details of the logging in the Windows application are shown. As can be seen the error originates from a web service call and information about which part of the application was affected by the error is shown. Further information can be found under Additional details.

UptoLog ApS - Aagade 17, 3 th - 9000 Aalborg - Denmark - Phone: +45 26812660 - E-mail: support@uptolog.com - CVR-number: 30 59 65 01