The following are best practices for running the Diagnostics Console and Diagnostics Service. These recommendations are intended to help preserve system performance and ensure compatibility between the Diagnostics Service and Diagnostics Console.
-
Logging a large amount of data in a production system can impede performance, so you should only log the minimum amount of traffic necessary to troubleshoot your current issue.
-
Having the Diagnostics Console open while a large amount of data is being logged can also affect performance, so the preferred approach is to configure the Diagnostics Service to log messages to a file and then analyze the file after you finish recreating the issue. For information about configuring the Diagnostics Service to log messages to a file, see .
-
To ensure compatibility, use the same version of both the Diagnostics Service and Diagnostics Console. The Diagnostics Service and Diagnostics Console change from version to version, so the same version of each should be used to take full advantage of all features.
-
Use the Save All Tabs feature when sending logs to technical support.