Performance Counter Data Collector creates new logs before they reach the maximum size configured in the Data Collector Set

Article ID: 2785845 - View products that this article applies to.
Expand all | Collapse all


When configuring a Performance Monitor Data Collector using the default template and a max file size for sequential file logging the BLG (perfmon log) files are truncated prematurely resulting in many small files rather than BLG files of the intended and configured maximum size for the data collector set.


This is caused by both the Kernel ETL Log and the Performance log using the same segmentation event. When the Kernel log reaches its defined maximum size, the Perfmon log will also be truncated.


To workaround this problem, follow the steps mentioned below:

  1. Delete the NT Kernel Trace from the collection set leaving only the Performance Counter trace. No kernel logger means it will not force segmentation of the Performance Counter Log files.
  2. Change the stop condition to be duration instead of max size. This segmentation problem relies on the size of the performance coutner log, so duraction constrained data collectors will not experience this issue.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.


Article ID: 2785845 - Last Review: November 22, 2012 - Revision: 1.0
Applies to
  • Windows Server 2008 R2 Service Pack 1
  • Windows Server 2008 Service Pack 2

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from