Partilhar via

View or change properties of a log or alert

  • Artigo

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

To view or change properties of a log or alert

  • Using the Windows interface

  • Using a command line

Using the Windows interface

  1. Open Performance.

  2. Double-click Performance Logs and Alerts.

  3. Click Counter Logs, Trace Logs, or Alerts.

  4. In the details pane, double-click the name of the log or alert.

  5. View or change the log properties as needed.

Notes

To perform this procedure, you must be a member of the Administrators group, or the Performance Log Users group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure. For more information, see Default local groups, Default groups, and Using Run as.

  • To open Performance, click Start, click Control Panel, double-click Administrative Tools, and then double-click Performance.

  • To start or stop a log or alert, right-click its name in the details pane, and click Start or Stop as appropriate. This overrides any scheduled start and stop settings, resetting the start and stop mode to manual.

Using a command line

  1. Open Command Prompt.

  2. Type the appropriate command below:

Action Command

To update counter log counters and the update interval.

logmanupdatecollection_name-c {path [path...]} | -cf {filename} -si[[hh:]mm:]ss

To update a counter log collection, file type, file size limits, path and name, and automatic naming parameters.

logman update collection_name-f {bin | bincirc | csv | tsv | SQL} -maxvalue-opath-v {nnnnn | mmddhhmm}

To update manual to automated start and stop methods and schedule.

logman update collection_name-b M/d/I h:mm:ss [AM | PM] -e M/d/yyyy h:mm:ss [AM | PM] -r

To update trace log providers and events to log.

logman update collection_name-p provider

To update a trace log collection, file type, file size limits, path name, and automatic naming parameters.

logman update collection_name-f {bin | bincirc} -maxvalue-opath-v {nnnnn | mmddhhmm}

To update a trace log's buffer size, limits, and transfer interval.

logman update collection_name-bs {value} -nb {min max} -ft [[hh:]mm:]ss
Value Description

update collection_name

Updates the collection query named collection_name. For counter collections, modifications to the query will stop, and then restart the collections.

-c {path [path...]} | -cf {filename}

Specifies the performance counter path to log (path), or specifies the path name of the log file that lists these counters (-cffilename). To list multiple counter paths, separate the command line by a space, or use the -cf option to list counter paths in an input file, one per line. Use this format [\\computer]\object[instance]\counter] for each counter path where:

Computer is the optional computer name or the IP address of a remote computer. If a computer name is not supplied, the local computer will be used by default.

Object is the performance counter object (process or memory).

Instance (if any) is the performance object (process).

Counter is the performance counter for the object (processor time).

-si[[hh:]mm:]ss

Specifies the update interval for counter collection in hours, minutes, and seconds.

-f bin | bincirc | csv | tsv | SQL

Specifies the file format used for collecting performance counter and trace data. You can use binary (bin), circular binary (circbin), comma (csv) and tab (tsv) separated, or SQL database (SQL) formats when collecting performance counters. If a file format is not specified, it defaults to binary. Binary (bin) and circular binary (circbin) are the only types supported for trace collections.

-max {value}

Specifies the maximum size of the collected log file in megabytes. If the log file exceeds the maximum size, the collection will stop. For a SQL database, the maximum size is the number of records to be written.

-opath

Specifies the path name of the output file that collects performance counter or trace data. By default, the collection log file name is the collection query name suffixed by either .blg for performance counters, or .etl for trace data.

-v {nnnnn | mmddhhmm}

Attaches the version control information to the end of the output file and path name. Use numeric nnnnn format, or date format mmddhhmm (month, day, 24-hour, minute) for version control.

-b M/d/yyyy h:mm:ss[AM | PM]

Specifies the begin-time for collections in a 24-hour format. You can also specify begin-time for collections in a 12-hour format by adding AM or PM in the command line. By default, the current day and time is used unless otherwise specified.

-e M/d/yyyy h:mm:ss[AM | PM]

Specifies the end-time for collections in a 24-hour format. You can also specify end-time for collections in a 12-hour format by adding AM or PM in the command line. By default, the current day and time is used unless otherwise specified.

-r-[-]r

Repeats the collection every day at the time periods specified by the -b and -e options. This is valid only for begin- and end-times specified on the same day, month, and year.

-[-]r turns off the repeat option.

-p {provider [flags [level]]}

Specifies the name of the provider.

-bs {value}

Specifies the buffer size in n kilobytes for the trace log.

-nb {minmax}

Specifies the minimum and maximum number of buffers for the trace log.

-ft[[hh:]mm:]ss

Specifies whether the buffer will be flushed, and the interval at which the buffer will be flushed.

Notes

To perform this procedure, you must be a member of the Administrators group, or the Performance Log Users group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure. For more information, see Default local groups, Default groups, and Using Run as.

  • To open a command prompt, click Start, point to All programs, point to Accessories, and then click Command prompt.

  • To view the complete syntax for this command, at a command prompt, type:

    logman /?

Information about functional differences

  • Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web.

See Also

Concepts

Set parameters for a log
Define start or stop parameters for a log or alert
Define actions for an alert
Define counters and thresholds for an alert
Logman