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:
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.
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.
perfmon Performance Logs BLG Kernel Tracing ETL