Server Logging
NCache provides another feature where clustered caches and client caches are logged into different log files. These files are created when a cache starts. These log files keep on logging data until that cache is stopped. Log files encapsulate different levels of information based on logging status.
Each log file is created against a particular cache with a different time span. This time span is the time from when the cache is started to the time when the cache is stopped. To give the user a readable format, NCache writes these log files with the default format. Also, whenever an operation is performed by a running thread, NCache logs the name of that thread in these files as well.
Server Logging Levels
NCache allows different stages of logging. These logging levels can be manually configured and are described below:
Detail DEBUG: This flag is disabled by default but the user can configure it. This log option prints detailed information about any operations in the cache such as information about each operation like key, and cache items, during state transfer. This log information is useful to analyze cache issues in detail whenever normal debugging is not possible. But this causes performance degradation for cache operations.
ERROR: This log flag gives the cause of errors that occurred during operation execution. This log level is quite useful during troubleshooting, for instance, the start of cache exception, which occurs for joining with its own replica.
See Also
Windows Event Logs
Cache Client Logs
Diskperf Not Installed
No READ Access to the Perflib Subkeys
Monitor Cache Client Counters