Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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

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

View products that this article applies to.

Symptoms

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.

↑ Back to the top

Cause

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.

↑ Back to the top

Workaround

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.

↑ Back to the top

Keywords: kb

↑ Back to the top

Article Info
Article ID : 2785845
Revision : 1
Created on : 1/7/2017
Published on : 11/22/2012
Exists online : False
Views : 224