Windows Server 2012 : Comprehensive Performance Analysis and Logging (part 7) - Performance logging - Creating and managing data collector sets

Performance logging

Windows Server 2012 uses data collector sets and reports. Data collector sets allow you to specify sets of performance objects and counters that you want to track. When you create a data collector set, you can easily start or stop monitoring the performance objects and counters included in the set. In a way, this makes data collector sets similar to the performance logs used in earlier releases of Windows. However, data collector sets are much more sophisticated. You can use them in the following ways:

• Use a single data set to generate multiple performance counter and trace logs.

• Assign access controls to manage who can access collected data.

• Create multiple run schedules and stop conditions for monitoring.

• Use data managers to control the size of collected data and reporting.

• Generate reports based on collected data.

In Performance Monitor, you can review currently configured data collector sets and reports under the Data Collector Sets and Reports nodes, respectively. As shown in Figure 13, you’ll find data sets and reports that are user defined and system defined. User-defined data sets are created by users for general monitoring and performance tuning. System-defined data sets are created by the operating system to aid in automated diagnostics.

Figure 13. Review the available data collector sets and reports.

Creating and managing data collector sets

Creating and managing data collector sets

In Performance Monitor, you can view the currently configured data collector sets by expanding the Data Collector Sets node and then expanding the User Defined and System nodes. When you select a data collector set in the left pane, you’ll see a list of the related data collectors in the main pane listed by name and type.

Data collector set types include the following:

• Configuration The Configuration type is for data collectors that record changes to particular registry paths.

• Trace The Trace type is for data collectors that record performance data whenever related events occur.

• Performance Counter The Performance Counter type is for data collectors that record data on selected counters when a predetermined interval has elapsed.

Windows Server 2012 uses event traces to track a wide variety of performance statistics. You can view running event traces by selecting Event Trace Sessions. You can then stop a data collector running a trace by pressing and holding or right-clicking it and selecting Stop.

Some event traces are configured to start automatically with the operating system. These event traces are called Startup Event Traces. You can view the enabled or disabled status of event traces configured to run automatically when you start the computer by selecting Startup Event Trace Sessions. You can start a trace by pressing and holding or right-clicking a startup data collector and selecting Start As Event Trace Session. You can delete a startup data collector by pressing and holding or right-clicking it and then selecting Delete.

You can save a data collector as a template that can be used as the basis of other data collectors by pressing and holding or right-clicking the data collector and selecting Save Template. In the Save As dialog box, select a directory, type a name for the template, and then tap or click Save. The data collector template is saved as an XML file that can be copied to other systems.

You can delete a user-defined data collector by pressing and holding or right-clicking it and then selecting Delete. If a data collector is running, you need to stop collecting data first and then delete the collector. Deleting a collector deletes the related reports as well.

Using data collector templates

Performance Monitor includes several preconfigured templates for gathering general diagnostics information, which can include information about the system configuration and performance:

• Basic Generates a report that will include basic information about the computer, CPU and disk utilization, and active network adapters. After you create a data collector set based on this template, you can add or remove counters and change the scheduling by editing the properties of the data collector set. When you are reviewing the data, be sure to drill down into the details. For example, under disks, examine the hot files, which are the files causing the most disk I/O activity. Also, be sure to closely examine the resource overview, which provides a summary analysis of CPU, network, disk, and memory usage. Note that this basic data is included in the reports for the other predefined collector sets. Default run time: 60 seconds.

• Active Directory Diagnostics Generates a report that provides detailed diagnostics data for Active Directory, which includes registry keys, performance counters, and trace events. On domain controllers, you can use this data to help troubleshoot Active Directory performance issues. Pay particular attention to the Active Directory diagnostics and tuning data provided in the report. For example, with searches, be sure to examine the detailed data provided for unique searches, directory search by object, search status codes, searches with the most CPU utilization, and clients with the most CPU usage. Also, don’t overlook the tuning parameters for the registry. Default run time: 300 seconds.

• System Performance Generates a report that provides detailed performance data regarding local hardware resources, system response times, and processes on the local computer. Use this information to identify the possible causes of performance issues. Note that the system performance data is included in the report for system diagnostics. Default run time: 60 seconds.

• System Diagnostics Generates a report that provides detailed diagnostics data, which includes the status of local hardware resources, system response times, and processes on the local computer along with system information and configuration data. Suggests ways to maximize performance and streamline system operation. Be sure to closely examine the entries under basic system checks, particularly those for hardware devices and drivers. Default run time: 60 seconds.

On member servers, system data collector sets are created automatically for system diagnostics and system performance. On domain controllers, a system data collector set for Active Directory diagnostics is also created. If you press and hold or right-click the related entry under Data Collector Sets and then select Start, Performance Monitor will generate a report that you can review to evaluate performance and begin diagnostics for troubleshooting.

Although you can’t modify the system data collector sets that were created automatically, you can create new collector sets based on the predefined templates and then modify their settings. To do this, follow these steps:

1. In Performance Monitor, under the Data Collector Sets node, press and hold or right-click the User Defined node in the left pane, point to New, and then choose Data Collector Set.

2. In the Create New Data Collector Set Wizard, type a name for the data collector, such as Custom System Diagnostics. The Create From A Template (Recommended) option is selected by default, as shown in Figure 14. Tap or click Next.

   

   Figure 14. Specify the name of the collector set and base the set on a template.

3. On the Which Template Would You Like To Use page, shown in Figure 15, select the template to use or click Browse to search for a saved template. When you are ready to continue, tap or click Next.

   

   Figure 15. Select a predefined template to use or browse for a saved template.

4. On the Where Would You Like The Data To Be Saved page, type the root path to use for logging collected data. Alternatively, tap or click Browse and then use the Browse For Folder dialog box to select the logging directory. Tap or click Next when you are ready to continue.

5. On the Create New Data Collector Set page, the Run As box lists <Default> as the user to indicate that the log will run under the privileges and permissions of the default system account. To run the log with the privileges and permissions of another user, tap or click Change. Type the user name and password for the desired account, and then tap or click OK. User names can be entered in DOMAIN\USERNAME format, such as CPANDL\WilliamS for the WilliamS account in the CPANDL domain.

6. Select the Open Properties For This Data Collector Set option, and then tap or click Finish. This saves the data collector set, closes the wizard, and then opens the related Properties dialog box.

7. By default, logging is configured to start manually. To configure a logging schedule, tap or click on the Schedule tab and then tap or click Add. You can now set the active range, start time, and run days for data collection. Figure 16 shows an example.

   

   Figure 16. Set the run schedule for the collector set.

8. By default, logging stops only if you set an expiration date as part of the logging schedule. Using the options on the Stop Condition tab, you can configure the log file to stop manually after a specified period of time, such as seven days, or when the log file is full (if you set a maximum size limit).

9. Tap or click OK when you finish setting the logging schedule and stop conditions.  If you want Windows to run a scheduled task when data collection stops, configure the tasks on the Task tab in the Properties dialog box.