Playing With Exchange 2013 Performance Logs

It's not common that one needs to play with Exchange 2013 daily performance log files on a daily basis, unless you work for Microsoft support. You will be hunting for it, especially if you have raised a ticket with performance issues with the Exchange support team.

More...

Anyone who has worked with Windows servers for long enough knows the importance of Performance monitor. It's a built in tool in Windows which comes in handy whenever you want to troubleshoot a performance issue, be it your connected storage or networks. The good thing is that Exchange 2013 logs performance data as part of it's extensive logging to make things easier for you. Hence if you have an odd issue which needs a performance trace (say users on a database experiencing very slow response from the server or an unexpected database failover), the data is available for you to analyze.

All we need is to know the location of the file and it's in C:\Program Files\Microsoft\Exchange Server\V15\Logging\Diagnostics\DailyPerformanceLogs by default, unless you have the Exchange binaries on a different location. You will have a couple of days worth of logs (depending on how long you keep the data) and these files are around a gigabyte in size.

[clickToTweet tweet="#MSExchange 2013 logs Perfmon data 24/7 out of the box!" quote="Exchange 2013 logs Perfmon data 24/7 out of the box !" theme="style3"]​

What if you need the current file that is getting written?

I ran into an issue where I wanted to get hold of the latest perfmon file, but it was the current file in use and was showing as zero kb in size.

Daily Perfmon Logs Current

In order to get hold of the file with the data, you need to open up Performance Monitor and stop the two jobs that are running - ExchangeDiagnosticsDailyPerformanceLog and ExchangeDiagnosticsPerformanceLog.

Stopping those two jobs populated the zero kb file with data and I was able to copy it to another location for analysis.

Starting both the services back created a new perfmon file, which became the current file recording the data.

Simple, but useful info at the right time. Has anyone ran into this before?

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.