Cisco unified communications manager real time monitoring tool rtmt

Informational Clusterwide total number of registered gateways increased in consecutive polls. Number of registered media devices on each server or for all servers in a cluster if applicable.

Warning Clusterwide total number of registered media devices decreased in consecutive polls. Informational Clusterwide total number of registered media devices increased in consecutive polls. The Device Search menu comprises the following items on which you can search: phones, gateway devices, H. You can search on any device in the Unified Communications Manager system and choose the status of the devices, including registered, unregistered, rejected, any status, and devices that are only configured in the database.

You can also search by any model, or a specific device model, and set up criteria that include several different attributes. Within the phone search, you can also search on the basis of phone protocol. You can also generate reports for your devices to troubleshoot them. Results display in a table with a row for each matched device, a column for each of the specified attributes, and a timestamp of the device that has been opened or closed and the application that controls the device media.

If you have Unified Communications Manager clusters and you search for a device by choosing the Any Status option, Unified RTMT does not display a snapshot of the matched device type, but rather it displays data for that device type from the Cisco RIS database for all specified Unified Communications Manager servers for a period of time.

When you see multiple entries of a device, the current status of the device reflects the entry that has the latest timestamp. The phone summary provides information about the number of registered phones, phones that are running SIP, phones that are running SCCP, partially registered phones, and the number of failed registration attempts.

Follow this procedure to monitor data for the following device types:. Perform one of the following tasks:. On the Quick Launch Channel, perform the following steps:. In the tree hierarchy, double-click Device. Click the Device Search icon. A device selection window displays where you enter the search criteria. The Device Search window displays the cluster names if applicable and tree hierarchy that lists all device types that you can monitor. To find all devices or to view a complete list of device models from which you can choose, right-click the cluster name and choose Monitor.

To monitor a specific device type, right-click or double-click the device type from the tree hierarchy. If you right-click the device type, you must choose Monitor for the device selection window to display. In the Select device with status window, click the radio button that applies. In the drop-down list box next to the radio button that you clicked, choose Any CallManager or a specific Unified Communications Manager server for which you want the device information to display.

In the Search by device model pane, click the radio button that applies. If you chose Device Model , choose the device type for which you want the device information to display. Click Next. In the Search with name pane, click the radio button that applies and enter the appropriate information in the corresponding fields, if required. In the Monitor following attributes pane, check one or all of the search attributes.

Click Finish. Some devices may not provide information for all search criteria. For example, if you select to monitor a phone for active load, inactive load, download status, or download reason, the download status results display Unknown for phone models that cannot provide this information. You can view information about phones that display in the RTMT device monitoring pane. This section describes how to view phone information.

Right-click the phone for which you want information to display and choose Open. In the Search By Device Model pane, choose the phone protocol that you want to display. Click the Any Model or Device Model radio button. If you click the Device Model radio button, choose a phone model that you want to display.

In the Search With Name pane, click the radio button that applies and enter the appropriate information in the corresponding fields. The Device Information window appears. For more information about the device, choose any field that appears in the left pane of the window. Devices or endpoints generate alarms for each critical event for diagnostics and troubleshooting. Use the Generate PRT option to remotely trigger the log collection on the phone and upload it to the log server configured in the "Customer support upload URL" parameter.

Right-click the phone for which you want information to display and choose Generate PRT. The generated report is uploaded at the Customer support upload URL. Else, PRT generation fails. You can view the properties of devices that appear in the RTMT device monitoring pane. Follow this procedure to view device properties. To display the device description information, click the Description tab. To display other device information, click the Other Info tab.

Unified Communications Manager polls counters, devices, and gateway ports to gather status information. In the RTMT monitoring pane, you configure the polling intervals for the performance monitoring counters and devices.

High-frequency polling rate may adversely affect Unified Communications Manager performance. The minimum polling rate for monitoring a performance counter in chart view is 5seconds; the minimum rate for monitoring a performance counter in table view is 1second. The default value for both is 10seconds. You can specify criteria for the CTI applications, devices, and lines that include CTI status, device name, application pattern, and attributes.

Results display in a table with a row for each matched device, a column for each of the specified attributes, and a time stamp of the device that has been opened or closed and the application that controls the device media. Follow this procedure to display a chart of open devices, lines, and CTI connections for each server or for each server in a cluster if applicable.

Perform the following procedure to find specific CTI applications to monitor:. In the tree hierarchy, double-click CTI. Click the CTI Search icon. From the Applications Status drop-down list box, choose the application status. In the Application Pattern pane, click the radio button that applies.

Enter the information in the field for the radio button that you clicked; for example, if you clicked the IP Subnet radio button, enter the IP address and the subnet mask in the field. In the Monitor following attributes window, check one or all of the check boxes for the attributes that you want to monitor.

The applications monitoring pane displays the information that you choose. Follow this procedure to find specific CTI devices to monitor. If you right-click the option, choose Monitor. From the Devices Status drop-down list box, choose the device status. In the Devices pane, click the radio button that applies. If you chose Device Name , enter the device name in the field.

In the Application Pattern window, click the radio button that applies. Enter the information in the field for the radio button that you clicked; for example, if you clicked IP Subnet , enter the IP address and subnet mask in the field. In the Monitor following attributes window, check one or all check boxes for the attributes that you want to monitor. The devices monitoring pane displays the information that you chose.

Follow this procedure to find specific CTI lines to monitor. From the Lines Status drop-down list box, choose the status. In the Lines pane, click the radio button that applies:.

If you chose Directory Number , enter the directory number in the field. In the Application Pattern pane, click the radio buttons apply:.

The lines monitoring pane displays the information that you choose. Follow this procedure to view application information. To view updated information, click Refresh. To close the window, click OK. When you configure the call control discovery feature, Unified Communications Manager advertises itself and its hosted DN patterns to other remote call-control entities that use the SAF network. Likewise, these remote call-control entities advertise their hosted DN patterns, which Unified Communications Manager can learn and insert in digit analysis.

The learned pattern may be repeated in the report because the learned pattern may be coming from a different source; for example, it may be coming from a different IP address. Learned Pattern reports include such information as learned pattern name, time stamp, and reachability status for the pattern. See the following table. Displays the name of the learned pattern from the remote call-control entity. Displays the date and time that the local Unified Communications Manager marked the pattern as a learned pattern.

Indicates whether the learned pattern was reachable or unreachable. Displays the name of the remote call-control entity that advertised the learned pattern. Displays the IP address for the call control entity that advertised the learned pattern; Displays the port number that the call-control entity uses to listen for the call.

Displays the PSTN failover configuration for the learned pattern. If None displays, you did not enter a description for the SAF forwarder. Displays the number of times that the call-control entity, in this case, the Unified Communications Manager, has attempted to connect to the SAF forwarder.

RTMT allows you to search based on different criteria; for example, if you specify a search for the remote call-control entity, all the learned patterns display for the remote call-control entity.

To access the report, perform one of the following actions:. Choose the node from the Select a Node drop-down list box. For learned pattern reports, if the Cisco CallManager Service is running but the CCD requesting service is not running on that node, a message displays that the CCD Report Service is not working after you choose the node. If the CCD requesting service is not active on the node that you choose, the report displays as empty. After the data appears, if you want to filter the results based on specific criteria, click the Filter button; specific the criteria that you want to search, click Apply and then OK.

To display the most current results, click Refresh. If you want to search on a specific string in the data, click the Find button, enter the string, then, click Find Next. If you want to save the results, click Save , and choose either XML or Text , depending on how you want to save the results. Browse to the location where you want to save the data, name the file that you want to save; then, click Save.

Called Party Trace allows you to configure a directory number or list of directory numbers that you want to trace. You can request on-demand tracing of calls using the Session Trace Tool. The Called Party Trace feature provides information on the calling party number in addition to the called party number within a node.

You can use the information from each node to trace a call back to the originator. You must be an authorized administrator to access the directory number logs. To grant authorization to a specific role using MLA, the "Called Party Tracing" resource must have read permission enabled for the role. When 5 megabytes of trace file entries have been written to the log files being accessed by RTMT, the oldest log information is overwritten by new trace entries as they are recorded.

The RTMT lists a maximum of entries for any given search. The Network Activity object displays these charts:. Because each physical Cisco Intercompany Media Engine server contains multiple nodes, the number that displays in the chart does not indicate the number of physical Cisco Intercompany Media Engine servers that participate in the IME distributed cache. The Server Activity object displays these charts:. These records can be used for validation of learned routes. Validations Pending: Displays the number of pending validations on the Cisco IME service as well as the threshold for validations.

In addition, the local time of the RTMT client application, not the back end server time, provides the basis for the time stamp in each chart. To zoom in on the monitor of a predefined object, click and drag the left mouse button over the area of the chart that interests you. The Intercompany Media Services monitoring category monitors the following items:. This total includes the following routes:. Learned routes that represent the phone numbers that the Cisco Intercompany Media Engine client learned and that exist in the Unified Communications Manager routing tables.

Unique domains of peer enterprises for which Cisco Intercompany Media Engine routes exist. Published routes that represent the number of direct inward dialing numbers DIDs that were published successfully to the IME distributed hash table across all Cisco Intercompany Media Engine services.

Rejected routes that represent the number of learned routes that were rejected because the administrator blocked them. This total includes the following types of calls:.

Calls that were attempted including calls that were accepted, busy, no answer, and failed. Calls that were set up that is, made by Unified Communications Manager and accepted by the remote party.

Calls that were accepted that is, received by Unified Communications Manager and answered by the called party. The Real-Time Monitoring Tool provides a set of important performance counters that assist you in monitoring the overall performance of the IM and Presence service and Cisco Jabber. Under IM and Presence Summary, review the following information:. Under Cisco Jabber Summary, review the following information:.

This number should rise and fall based on the usage patterns of your deployment. Further investigation may be required if this number is higher than expected for your user base. The Presence Engine PE , which provides presence composition services and rich, always-on, network presence, creates an IM session on behalf of all users at PE start-up time.

This is necessary so that network presence events such as Unified Communications Manager Telephony Presence and Exchange Calendar notifications are reflected in a user's presence even if that user is not logged in to any IM clients. This counter gives the total number of IM packets handled by the IM and Presence node across all users.

For example, Alice's privacy rules will be applied to the IM packet before it is delivered to Bob, and then Bob's privacy rules will be applied to the IM packet before it is delivered to Bob's client. Whenever IM and Presence handles an IM packet it is counted once for the originator and once for the terminator. This counter gives the total number of IM packets handled by the IM and Presence node across all users in the past 60 seconds. This counter is reset to 0 every 60 seconds.

Monitoring of this counter will help identify the busy IM hours in your organization. These per session counters only exist for the duration of an IM session or user login. One set of these counters exists for each Presence Engine network presence session, and one set of these counters exists for each client login session.

These counters can be accessed from the CLI using the following command:. Every user assigned to an IM and Presence node that is logged into the system will have a set of JSM session counters for their current logged in client session and also their Presence Engine network session.

Updating these counters with new values as they change would place the system under stress. This counts the total number of IM packets sent by the user from his IM client or session. This counts the total number of IM packets sent to the user on his IM client or session. This counter represents the total number of Text Conferencing rooms hosted on the node. This includes both ad hoc rooms and persistent chat rooms. This counter represents the total number of AdHoc chat rooms currently hosted on the node.

Note that AdHoc chat rooms are automatically terminated when all users leave the room, so this counter should rise and fall in value regularly. This counter represents the total number of persistent chat rooms hosted on the node. Persistent chat rooms must be explicitly terminated by the room owner.

You can monitor this counter to identify if the total number of persistent chat rooms is very large and also to help identify if some persistent chat rooms are not being used regularly anymore. These pre-chat room counters exist only for the lifetime of a chat room. For ad hoc chat rooms, these counter instances are deleted when the Ad Hoc chat room is terminated. For persistent chat rooms, the counter instances are also deleted when the persistent chat room is terminated, however persistent chat rooms are long-lived, so they should rarely be terminated.

You can use these per-chat room counters to monitor the usage and participants in persistent and ad hoc chat rooms over their lifetime and can help identify persistent chat rooms that are no longer being used frequently. This counter gives the current number of occupants of the chat room. Monitor this counter for Persistent Chat rooms to get an indication of the usage trend for the chat room. Each of these rooms will have its own set of Per-Chat Room counters.

Similar to JSM Session counters, updating these with new values as they change would place the system under stress. The number of idle processes can drop to zero on occasion and is not a cause for concern.

However, if the number of idle processes are consistently below 5 processes, then it is an indication that the IM and Presence Server is being heavily loaded and requires further investigation. The Port Monitor lets you monitor the activity of each Cisco Unity Connection voice messaging port in real time. This information can help you determine whether they system has too many or too few ports. After the authentication succeeds, Unified RTMT launches the monitoring module from local cache or from a remote node, when the local cache does not contain a monitoring module that matches the back-end version.

When prompted, add the certificate store by clicking Yes. If you sign in using the single sign-on feature, Unified RTMT prompts once for a username and password after you click any one of the following menus:. Analysis Manager. After this happens, you must manually restart the program as an administrator.

A single copy of Unified RTMT that is installed on your computer lets you monitor more than one server or more than one cluster at a time. For example, you can monitor all of the following entities:. An IM and Presence Service on one node. A node on a cluster to monitor the health of the cluster. To monitor a product on a different node, you must use a new instance of Unified RTMT that is installed. Multiple copies of Unified RTMT that are installed on your computer let you simultaneously monitor multiple IM and Presence Services that are installed on different nodes.

Because installing another copy of Unified RTMT overwrites the shortcut icon, you should complete the following tasks:. Create another icon by creating a shortcut to jrtmt. If the installation detects another version in the selected folder, a message displays. To continue the installation, install the version in a different folder. Menu bar : the menu bar includes some or all of the following options, depending on your configuration:.

You can use the Cisco Unified Reporting application to snapshot cluster data for inspection or troubleshooting. Allows you to monitor system summary, monitor server resources, work with performance counters, work with alerts, collect traces, and view syslog messages.

Allows you to view Unified Communications Manager summary information on the server; monitor call-processing information; and view and search for devices, monitor services, and CTI.

Allows you monitor server and network activity of the Cisco Intercompany Media Engine server. Allows you to configure categories for table format view , set the polling rate for devices and performance monitoring counters, hide the quick launch channel, and edit the trace setting for RTMT.

Depending on your configuration, allows you to browse the applicable web pages for administration interfaces, Cisco Unified Serviceability , and Cisco Unity Connection Serviceability. Quick Launch channel : Pane that displays information about the server or information about the applications. The tab contains groups of icons that you can click to monitor various objects. Monitor pane : Pane where monitoring results are displayed. The counters contain simple, useful information about the system and devices on the system, such as number of registered phones, number of active calls, number of available conference bridge resources, and voice messaging port usage.

You can monitor the performance of the components of the system and the components for the application on the system by choosing the counters for any object by using the Cisco Unified Real-Time Monitoring Tool. The counters for each object display when the folder expands. RTMT integrates with existing software for performance monitoring:. RTMT provides alert notifications for troubleshooting performance. It also periodically polls performance counter to display data for that counter.

You can choose to display perfmon counters in a chart or table format. Performance monitoring allows you to perform the following tasks:.

Continuously monitor a set of preconfigured objects and receive notification in the form of an email message. Associate counter threshold settings to alert notification. An email or popup message provides notification to the administrator. Save and restore settings, such as counters that are being monitored, threshold settings, and alert notifications, for customized troubleshooting tasks. The Real-Time Monitoring Tool provides a set of default monitoring objects that help you to monitor the health of the system.

Default objects include performance counters or critical event status for the system and other supported services. The system summary in Unified RTMT allows you to monitor important common information in a single monitoring pane. In system summary, you can view information about the following predefined objects:.

The Server category monitors CPU and memory usage, processes, disk space usage, and critical services for the different applications on the server.

The percentage of CPU equals the total time that is spent executing in all the different modes and operations excluding the Idle time. The Process monitor provides information about the processes that are running on the system. The Disk Usage monitoring category charts the percentage of disk usage for the common and swap partitions. If more than one logical disk drive is available in your system, the system stores CTI Manager traces in the spare partition on the first logical disk and Cisco CallManager traces on the second logical disk.

The Critical Services monitoring category provides the name of the critical service, the status whether the service is up, down, activated, stopped by the administrator, starting, stopping, or in an unknown state , and the elapsed time during which the services are up and running on the system. The service currently exists in start mode, as indicated in the Critical Services pane and in Control Center in Cisco Unified Serviceability. The service currently remains stopped, as indicated in the Critical Services pane and in Control Center in Cisco Unified Serviceability.

The service stopped running unexpectedly; that is, you did not perform a task that stopped the service. The Critical Services pane indicates that the service is down. The CriticalServiceDown alert is generated when the service status equals down. You performed a task that intentionally stopped the service; for example, the service stopped because you backed up or restored your system, performed an upgrade, or stopped the service in Cisco Unified Serviceability or the CLI.

The service does not exist in a currently activated status, as indicated in the Critical Services pane and in Service Activation in Cisco Unified Serviceability. The system cannot determine the state of the service, as indicated in the Critical Services pane.

RTMT contains ready-to-view, predefined performance counters. You can also select and add counters to monitor in RTMT using performance queries. RTMT displays performance counters in chart or table format. Chart format presents a miniature window of information. You can display a particular counter by double-clicking the counter in the perfmon monitoring pane. Attributes for predefined performance counters, such as format and category, remain fixed.

You can define attributes for counters that you configure in RTMT. Because chart view represents the default, you can configure the performance counters to display in table format when you create a category. A category comprises a group of monitored performance counters. A tab in the RTMT monitoring pane contains the category name.

All performance counters that are monitored in this tab belong to a category. The system polls the performance counters in the tab at the same rate, with each category configured to have its own polling rate.

You can create custom categories in the RTMT monitoring pane to view information that helps you troubleshoot specific performance, system, or device problems. If your system is experiencing performance problems with specific objects, create custom categories to monitor the performance of the counters within the object.

If the system is experiencing problems with specific devices, create custom categories to monitor the devices in your system. In addition, you can create alert notifications for counters and gateways in these custom categories.

To create custom categories, you add a new category tab. When the tab is created, you specify the specific performance counters, devices, and alerts within that tab and then save your custom category by using Profile. The application polls the counters, devices, and gateway ports to gather status information. The polling rate in each precanned monitoring window remains fixed, and the default value specifies 30 seconds.

If the collecting rate for the AMC Alert Manager and Collector service parameter changes, the polling rate in the precanned window also updates. In addition, the local time of the RTMT client application and not the backend server time, provides the basis for the time stamp in each chart. In the RTMT monitoring pane, you configure the polling intervals for the applicable performance counters, devices, and gateway ports for each category tab that you create.

High-frequency polling rate affects the performance on the server. The minimum polling rate for monitoring a performance counter in chart view is 5 seconds; the minimum rate for monitoring a performance counter in table view is 5 seconds. The default for both specifies 10 seconds. To get a closer look at perfmon counters, you can zoom in on a perfmon monitor counter in the RTMT. To zoom in on a counter, perform one of the following tasks:. Drag the mouse over the plot area in the counter to frame the data and release the mouse button.

The counter zooms in the chart. Click the counter. The counter zooms in. Double-click the counter that you want to zoom. The box with the counter appears highlighted and the Zoom window launches.

The minimum, maximum, average, and last fields show the values for the counter since the monitoring began for the counter. Click the counter to select the counter to zoom. The box with the counter appears highlighted. The Zoom window launches. To zoom out a counter, perform one of the following actions:. The highlight feature helps to distinguish hosts and counters when multiple nodes or counters display on color-coded graphs.

To highlight charts and graphs, perform one of the following tasks:. Right-click any color code in the table below the chart in the Performance Log Viewer and choose Highlight to highlight the data series for that counter. Right-click any color code in the table below the chart in the Performance Log Viewer and choose Change Color to select a different color for the counter.

To return a highlighted item to its original appearance in the Performance Log Viewer, select another item to highlight. Counter properties allow you to display a description of the counter and configure data-sampling parameters. The Counter Property window contains the option to configure data samples for a counter. The performance counters that display in the Unified RTMT performance monitoring pane contain green dots that represent samples of data over time.

You can configure the number of data samples to collect and the number of data points to show in the chart. When you activate the Alert Notification feature, the application notifies you of system problems.

Perform the following configuration setup to activate alert notifications for a system counter:. Determine the threshold for the alert for example, an alert activates when calls in progress exceed the threshold of over calls or under 50 calls. Determine the frequency of the alert notification for example, the alert occurs once or every hour.

Determine the schedule for when the alert activates for example, on a daily basis or at certain times of the day. The Trace and Log Central feature in RTMT allows you to configure on-demand trace collection for a specific date range or an absolute time.

You can collect trace files that contain search criteria that you specify and save the trace collection criteria for later use, schedule one recurring trace collection and download the trace files to a SFTP or FTP server on your network, or collect a crash dump file. From Cisco Unified Serviceability, you can also edit the trace setting for the traces on the node that you have specified.

Enabling trace settings decreases system performance; therefore, enable Trace only for troubleshooting purposes. After you collect the files, you can view them in the appropriate viewer within the real-time monitoring tool. You can also view traces on the node without downloading the trace files by using the remote browse feature. You can open the trace files by either selecting the internal viewer that is provided with Unified RTMT or choosing an appropriate program as an external viewer.

For devices that support encryption, the SRTP keying material does not display in the trace file. The Collect Files option in Trace and Log Central collects traces for services, applications, and system logs on the server or on one or more servers in the cluster.

The services that you have not activated also appear, so you can collect traces for those services. RTMT supports the throttling of critical Trace and Log Central operations and jobs, whether they are running on demand, scheduled, or automatic. If the goal the value of the service parameter is lower than the actual value, the system displays the warning.

After you log in to a server, RTMT launches the monitoring module from the local cache or from a remote server when the local cache does not contain a monitoring module that matches the back-end version. RTMT includes a default configuration that is called Default. The first time that you use RTMT, it uses the Default profile and displays the system summary page in the monitor pane. Unified Communications Manager clusters only: Default profile also dynamically monitors all registered phones for all Unified Communications Manager servers in a cluster.

If your cluster contains five configured Unified Communications Manager servers, CM-Default displays the registered phones for each server in the cluster, as well as calls in progress and active gateway ports and channels. You can configure RTMT to display the information that interests you, such as different performance counters for different features, in the monitor pane of RTMT and save the framework of your configuration in a profile.

You can then restore the profile at a later time during the same session or the next time that you log in to RTMT. By creating multiple profiles, so each profile displays unique information, you can quickly display different information by switching profiles. If you are running the RTMT client and monitoring performance counters during a Unified Communications Manager upgrade, the performance counters will not update during and after the upgrade.

Categories allow you to organize objects in RTMT, such as performance monitoring counters and devices. For example, the default category under performance monitoring, RTMT allows you to monitor six performance monitoring counters in graph format. If you want to monitor more counters, you can configure a new category and display the data in table format. If you perform various searches for devices, for example, for phones, gateways, and so on, you can create a category for each search and save the results in the category.

The statistics that are collected include comprehensive information that you can use for system diagnosis. The system automatically enables troubleshooting perfmon data logging to collect statistics from a set of perfmon counters that provides comprehensive information about the system state. When you enable Troubleshooting Perfmon Data Logging, Cisco estimates that the system experiences a less than five percent increase in CPU utilization and an insignificant increase in the amount of memory that is being used, and it writes approximately 50 MB of information to the log files daily.

You can perform the following administrative tasks with the troubleshooting perfmon data logging feature:. Monitor a set of predefined System and performance objects and counters on each server. Specify the polling rate. This rate specifies the rate at which performance data is gathered and logged.

You can configure the polling rate down to 5 seconds. Default polling rate equals 15 seconds. View the log file in graphical format by using the Microsoft Windows performance tool or by using the Performance Log viewer in the Real-Time Monitoring Tool.

Specify the maximum number of log files that will be stored on disk. Log files exceeding this limit are purged automatically by removal of the oldest log file.

The default specifies 50 files. Specify the rollover criteria of the log file based on the maximum size of the file in megabytes. The default value specifies 2 MB. The troubleshooting perfmon data-logging feature collects information from the following counters within the following perfmon objects. Follow this procedure to collect information from counters within the perfmon objects with the perfmon data-logging feature.

Select the server from the Server list box. Enter the appropriate settings as described in the following table. From the drop-down list box, select True to enable or False to disable troubleshooting perfmon data logging.

The default value specifies False. Enter the polling rate interval in seconds. You can enter a value from 5 minimum to maximum. The default value specifies Enter the maximum number of Troubleshooting Perfmon Data Logging files that you want to store on disk.

You can enter a value from 1 minimum up to maximum. Consider your storage capacity in configuring the Maximum No. When the number of files exceeds the maximum number of files that you specified in this field, the system deletes log files with the oldest time stamp. If you do not save the log files on another computer before you change this parameter, you risk losing the log files. Enter the maximum file size in megabytes that you want to store in a perfmon log file before a new file is started.

You can enter a value from 1 minimum to maximum. Select Save. Skip to content Skip to search Skip to footer. Book Contents Book Contents. Find Matches in This Book. PDF - Complete Book 6. Updated: October 12, Chapter: Performance Counters.

Tip You can display up to three counters in one chart in the Perfmon Monitoring pane. Step 2 Click the name of the server where you want to add a counter to monitor. Step 3 To monitor a counter in a table format, continue to step 4. Step 5 In the Enter Name field, enter a name for the tab. Step 6 To display the perfmon counters in table format, check the Present Data in Table View check-box.

Step 7 Click OK. Step 8 Perform one of the following actions to select one or more counters with one or more instances for monitoring in table format skip the remaining step in this procedure : Double-click a single counter and select a single instance from the dialog box, and then click Add. Double-click a single counter and select multiple instances from the dialog box, and then, click Add.

Tip To display the counter in a chart format after you display it in a table format, right-click the category tab and choose Remove Category. Step 9 To monitor a counter in a chart format, perform the following tasks: Click the file icon next to the object name that lists the counters that you want to monitor. A list of counters appears.

The counter chart appears in the Perfmon Monitoring pane. Procedure Perform one of the following tasks: Right-click the counter that you want to remove and choose Remove. Add Counter Instance Follow this procedure to add a counter instance.

Procedure Step 1 Find and display the performance monitoring counter. Step 3 In the Select Instance window, click the instance, and then click Add. The counter appears. Set Up Counter Alert Notification Follow this procedure to configure alert notification for a counter. Tip To remove the alert for the counter, right-click the counter and choose Remove Alert. Procedure Step 1 Find and display the performance counter. Step 3 Check the Enable Alert check box.

Step 4 In the Severity drop-down list box, choose the severity level at which you want to be notified. Step 5 In the Description pane, enter a description of the alert and click Next. Step 7 To configure the system to send an e-mail message for the alert, check the Enable Email check box. Step 8 To trigger an alert action that is already configured, choose the alert action that you want from the Trigger Alert Action drop-down list box.

Step 9 To configure a new alert action for the alert, click Configure. Note Whenever the specified alert is triggered, the system sends the alert action. Step 10 To add a new alert action, click Add. Step 11 In the Name field, enter a name for the alert action. Step 12 In the Description field, enter a description for the alert action. Step 13 Click Add to add a new e-mail recipient for the alert action.

The Input dialog box appears. Step 14 Enter either the e-mail or e-page address of the recipient that you want to receive the alert action notification and click OK Step 15 In the User-defined email text box, enter the text that you want to display in the e-mail message and click Activate. Display Counter Description The following shows how to obtain a description of the counter: Procedure Step 1 Perform one of the following tasks: In the Perfmon tree hierarchy, right-click the counter for which you want property information and choose Counter Description.

Tip You can display the counter description and configure data-sampling parameters. Step 2 If you are displaying perfmon counters in the chart format, right-click the graph for which you want data sample information and choose Start Counter s Logging.

Step 3 If you want to log all counters in a screen both chart and table view format , you can right-click the category name tab at the bottom of the window and choose Start Counter s Logging. Step 4 Configure the maximum file size and maximum number of files parameter. Note If you have already started logging perfmon counters and you want to change the maximum file size and maximum number of files, you must first stop the counters before you reconfigure the maximum file size and number of files parameters.

After resetting the parameters, you can then restart logging perfmon counters. Stop Perfmon Counter Logging To stop logging perfmon counter data, perform the following procedure: Procedure Step 1 Find and display the performance monitoring counters.

Step 2 If you are displaying perfmon counters in the chart format, right-click the graph for which counter logging is started and choose Stop Counter s Logging. Configure Data Sample The Counter Property window contains the option to configure data samples for a counter.

Procedure Step 1 Find and display the counter. Step 3 To configure the number of data samples for the counter, click the Data Sample tab. Step 4 From the No. The default specifies Step 5 From the No. Step 6 Click one of the following parameters: Absolute: Because some counter values are accumulative, choose Absolute to display the data at its current status. View Counter Data Follow this procedure to view the data that is collected for a performance counter.

Step 2 Choose View All Data. Step 3 Right-click the counter that currently appears. Step 4 Choose View Current. Log files on Perfmon Log Viewer and Microsoft Performance Tool The performance log viewer displays a chart with the data from the selected counters.

Table 1. Performance Log Viewer Button Function Select Counters Allows you to add counters that you want to display in the performance log viewer.