Configuring a Data Collector Set
To access the properties for a DCS, right-click the name of the DCS and select Properties from the shortcut menu. All of the properties for a data collector are configured from this interface. Properties available on each tab include the following:
- General Configure the data collector description, any keywords that are desired for search purposes, and the Run As properties that determine under what user context this DCS will run. Click Change to change the user context for the collector. The default is the Local System account.
- Directory Configure the root directory for the DCS and specify a separate subdirectory
if desired. The default is %SystemDrive%\perflogs\<Data Collector Set name>. You
can also specify the format of the subdirectory name based on the following options:
- Date and time Choose from the available subdirectory name formatting options that are displayed.
- Computer name You can also prefix the subdirectory with the computer name by selecting the Prefix Subdirectory With Computer Name check box.
- Serial Number You can use the Serial Number format (N) to create a unique
subfolder name each time the DCS is started. This allows multiple logs of the same
data collectors to be saved within different subfolders in the parent DCS folder. You
can edit the serial number only in the Data Collector Set Properties, but the serial
number format may also be specified to be used by individual data collectors. The
default DCS subdirectory naming convention is NNNNNN, which results in DCS
subfolders named 00000x (where x is the serial number).
For example, a DCS with a serial number of 8 that was run on January 31, 2003 at 4:20 A.M. would have the following results based on the selected subdirectory name format:
Subdirectory name format: yyyyMMddNNNN; Actual subdirectory name: 200301310008
Subdirectory name format: yyDDD NN; Actual subdirectory name: 03031 08
Subdirectory name format: MMMM MM\, yyyy \a\t h mmtt \- N; Actual subdirectory name: January 31, 2003 at 4 20 AM - 8
- Security Specify security parameters on the DCS. Default permissions are granted to SYSTEM, Administrators, Performance Log Users, and the data collector creator/owner.
- Schedule Configure the beginning date, expiration date, and launch time and day. Click Add to configure a schedule.
- Stop Condition Define when the data collection will stop. Options available on this
tab include the following:
- Overall Duration Configures the log to stop after a defined duration in seconds, minutes, days, hours, or weeks.
- Limits Defines limits for the log size or duration and whether to restart the DCS when those limits are reached. You can set the time duration or maximum size limit.
- Task Configure a specific task to run when a DCS stops. The specified task must be an existing Task Scheduler task. You can also specify the task arguments and the working directory.
Note You can also view and edit the properties of each data collector within a DCS by using the shortcut menus for each data collector. The configuration settings for a data collector vary depending upon whether the data collector is used for collecting performance counter, event tracing, or registry information.
In this tutorial:
- Windows 7 Desktop Maintenance
- Performance Monitoring
- Improvements to Performance Monitoring in Windows 7
- Using Performance Monitor
- Real-Time Performance Monitoring
- Performance Monitor Logging
- Creating a Data Collector Set
- Configuring a Data Collector Set
- Using Data Manager to View Performance Data
- Starting and Stopping Data Logging
- Viewing Performance Data
- Comparing Performance Monitor Logs
- Performance Monitor User Rights
- Remote Data Collection
- Using Windows PowerShell for Performance Monitoring
- Resource Monitor
- Overview Tab
- CPU Tab
- Memory Tab
- Disk Tab
- Network Tab
- Reliability Monitor
- How Reliability Monitor Works
- Windows Performance Tools Kit
- Event Monitoring
- Understanding the Windows Event Architecture
- Channels
- Improvements to Event Monitoring in Windows 7
- Using Event Viewer
- Understanding Views
- Viewing Event Logs
- Saving Event Logs
- Configuring Event Subscriptions
- Considerations for Workgroup Environments
- Creating a New Subscription
- Using the Windows Events Command-Line Utility for Event Monitoring
- Using Windows PowerShell for Event Monitoring
- Using Task Scheduler
- Improvements to Task Scheduler in Windows 7
- Understanding Tasks
- Understanding the Task Scheduler Architecture
- Understanding Task Scheduler Security
- Credentials Management
- Securing Running Tasks
- Understanding AT and Task Scheduler v1.0 Compatibility Modes
- Understanding the Task Scheduler Snap-in
- Understanding Default Tasks
- Creating Tasks
- Defining Triggers
- At Startup Trigger
- On Connection To AND Disconnect From User Session Triggers
- On Workstation Lock AND Unlock Triggers
- Defining Actions
- Defining Conditions
- Defining Settings
- Managing Tasks
- Viewing History
- Using SchTasks.exe for Creating and Managing Tasks
- Task Scheduler Events
- Troubleshooting Task Scheduler
- Tasks Won't Run If the Service Is Not Started
- The Task Will Run Only When a Certain User Is Logged On
- The Task Action Failed to Execute
- Interpreting Result and Return Codes
- Understanding the Windows System Assessment Tool
- Understanding WinSAT Assessment Tests
- Examining the WinSAT Features Assessment
- Running WinSAT from the Command Line
- Understanding WinSAT Command Exit Values
- Running WinSAT Using Performance Information and Tools
- System Capabilities Section
- OEM Upsell And Help Section
- Understanding Windows Error Reporting
- Overview of Windows Error Reporting
- How WER Works
- Store Management System
- ReportArchive Folder
- WER Service
- Understanding the Error Reporting Cycle
- Understanding WER Data
- Configuring WER Using Group Policy
- Configuring WER Using the Action Center