Lync centralized logging is a great new feature with Lync Server 2013. This feature also allows you to configure AlwaysOn logging, which will keep logging on, always J This is helpful in situations where an issue has been reported and you are not able to reproduce, or do not want to bother users to reproduce.
The commands for configuring centralized logging allow you to specify file locations, rollover time limits and sizes. However, these settings are only for when a user initiates a logging session. The AlwaysOn logging files are stored as part of the network service account, and in order to locate these ETL files, you must navigate to the following folder, by default:
When ALwaysOn is enabled, you will notice a series of HDR, Cache and ETL files stored in this folder. See the screenshot below for an example.
These files are not actually of any use to most people, and in order to extract data from them, you must run the Search-CsClsLogging cmdlet.
It is important to understand where these files are, and the impact they will have on your disk space. By default, they are stored on the system drive, and at this time I am not aware of any way to change that. The Set-CsClsConfiguration
cmdlet can be used to adjust file size and rollover limits here. This also allows you to specify a time period to store the cache files, which would include the temp files stored for NetworkService as part of AlwaysOn.