This article goes into a bit more depth on the various settings with examples on using filtering and processing trace files from other environments. The default Global Options are typically sufficient for a brief capture in a pilot or test environment, but in environments with active users the log files can get large quite quickly, especially when verbose logging is enabled.
Since the default Type is set to Circular once the log file reaches the Maximum Size 20 MB then old data is overwritten; this can make for a unhelpful trace file.
Be careful with this setting though as forgetting to stop the trace can eventually use up all available memory on the server. Leaving circular logging enabled the majority of the time is a safer approach. Be aware that the server does not start logging data immediately, there is typically a second delay before data begins to be recorded.
This is not normally noticeable but the behavior can be seen if the Real Time Option is Enabled. Either way it recommended to wait a few second before beginning the test scenario otherwise the initial SIP messages may not be captured. Once the logging has been stopped the trace data stored in memory is then written to one or more Event Trace Log. This example shows that when the previously set Maximum Size value of 50MB was reached a second log file was created.
The OCSLogger. But for all other uses outside PSS an additional step is required to convert the trace files into text. Both of these buttons along the bottom of the Logging Tool perform the same initial action: converting the binary ETL data into a flat text file. This text file will typically be about three times larger than the binary ETL file.
Additionally the flat text file can usually be compressed with a ratio since it is just ANSI text data. But if not simply packaging a text file for someone else to review then viewing the log data using Notepad is a quick way to go blind trying to figure out what is actually happening. Once this package is installed on the Lync Server then the Analyze Log Files option from the Logging tool can be used to open the converted trace text file in Snooper instead of Notepad.
The output file will be opened automatically in Snooper. Typically only the Messages need to be viewed for troubleshooting. When running trace captures in pilot or small environments it is typically easiest to just use the default settings mixed with customizing the log file size and type. But when troubleshooting issues in production Lync deployments these log files can grow very large fast and quickly become unmanageable.
The Edit Filters window contains both Include and Exclude filters to help narrow down the captured data. As an example only data related to a specific Lync user placing calls into the Exchange UM server should be logged.
If an ETL file from another server or Lync environment needs to viewed usually Microsoft PSS needs to do this with a separate tool, discussed earlier in this article. But the Lync server Logging Tool actually has an executable switch to allow it to analyze log files not captured directly from that server. Normally if an ETL file was simply just dragged into the default tracing folder the tool will be unable to either recognize or open that file.
But if the logging tool is manually launched with the PSS switch enabled then it will allow conversion and viewing of this file. About Jeff Schertz Site Administrator. Nice job, Jeff. Enough documentation on how to effectively use it and when? Not EVEN close. Hey, maybe we should do that — write a book on this? Hi, Thanks for the nice article. However i get the old logs instead of the logs during my test time.
For examples, i started the log on PM and stopped at PM, and analyzed the log. In the messages tab, i see logs from AM to almost am only. Its not showing the time i tested. What could be wrong? I would delete all the files in the tracing directory before starting a new trace, as well as look into enabling filtering as you may be capturing a LOT of data. I noticed the same thing when I was analizing the logs. To fix it, browse to the location of the log files 2 times.
The second time it will stick. Step 10 Select the Messages tab and click on any message to view its contents. Enable and View Microsoft Lync Client Logs Use the following procedure to enable client logging and view the resulting logs.
Step 2 Click on the drop-down arrow on the top right of the window. Step 4 Select General from the left pane. Step 6 Select OK. Step 7 Exit the Lync client. Do not just sign out of the Lync client. Step 9 Select all files in this directory and delete them.
Step 10 Sign in to the Lync client. Step 11 Complete a sign in or call attempt from the Lync client. Step 12 Exit the Lync client. Note The Communicator-uccapi-0 file contains logs for SIP messaging and other client-related logging information. Was this Document Helpful? Yes No Feedback. Latest commit.
Git stats 3 commits. Failed to load latest commit information. View code. Centralised Logging Tool features: The tool has the ability to manage logging on multiple Pools at once. About lyncskype-for-business-centralised-logging-tool Resources Readme. Releases 1 Version 1. May 8, Packages 0 No packages published. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window.
0コメント