TFS 2013 : Diagnostics and Troubleshooting
While working with TFS 2010 we had to go to TFS db directly to get the diagnostic information. TFS DB table named tbl_Command hosts this information. It was sort of a hidden information as if you don’t have access to db, you will not know if it is there; wasting time in finding solutions somewhere else. But with TFS 2012 and TFS 2013 release we also get a separate view for this diagnostic data as part of TFS Web Access portal.
You have to visit : http://<tfsservername>/tfs/_oi/ to land directly on to the diagnostic data.
This view lists all the activities performed by various TFS components like: WorkItem Tracking, Version Control, Framework, Team Configuration Service, Web Access etc.
Activity Log Entry Details
You can even get even more details regarding log entry by double clicking on one. A dialog will pop up for the same. You can get the details like which process, running on which machine, actually generated this event. This is helpful in case this even is generated by some custom tool which is built using TFS client APIs.
This view details about the background jobs which run regularly. So this gives you Job Summary, Job Queue, Job History.
The chart below displays total amount of run time this particular job has taken over the time period. Click on any of the bars in the chart to get the list of jobs contributing to the total.
The chart below displays the number of times a job has run combined with the number of result types for that particular job.
The chart below combines the average queue time and run time for jobs; you can also view how many jobs were run at each hour.
Note that you to see this diagnostic information user should be part of “Team Foundation Administrators” Group. But that will not be a good practice to put everyone into that group. Better option will be to create a new security group in TFS. lets say, “TFS Troubleshooters”. And make specific users/groups part of that group.