Summary

This chapter considered the technologies to use and best practices to follow when you add logging features to your distributed system. In the real world, these designs are neglected far too often, leading to countless headaches when problems occur in an application that lacks a sufficient way to record them.

You should always consider these three final guidelines:

  • Test your exception handling and logging code.

    Some reports suggest that logging code typically contains the highest concentration of errors relative to any other part of an application because it is seldom properly tested.

  • Quantify your theory with stress testing.

    Unless you put your system under a heavy load and watch the performance counters, you won’t know what unique bottlenecks ...

Get Microsoft® .NET Distributed Applications: Integrating XML Web Services and .NET Remoting now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.