Where is rtmt

Why is it meaningful, and what settings did you use to create it? I could be way off. That does not seem right to me. So could you please explain how do we avoid this alert normally? You can also look at the following for more information:. You must be logged in to post a comment. Alerts RTMT can be configured to monitor basic thresholds and then trigger an alert when a specific threshold is violated.

Twitter 0 Linkedin 0 X. Anthony, I believe alerts are managed from the server. Regards, Bill. Thanks JO. Jamal, If not exact, they are very similar. Thank you very much. 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.

Changes to the profile settings for the default profile on IM and Presence Service are not transferred to Unified Communications Manager. The system generates alert messages to notify administrators when a predefined condition is met, such as when an activated service goes from up to down. Alerts can be sent out as email or epage. Unified RTMT, which supports alert defining, setting, and viewing, contains preconfigured and user-defined alerts. Although you can perform configuration tasks for both types, you cannot delete preconfigured alerts whereas you can add and delete user-defined alerts.

Alert Central: This option comprises the history and current status of every alert in the system. You can also access Alert Central by selecting the Alert Central icon in the hierarchy tree in the system drawer.

Clear Alerts: This menu category allows you to reset an alert change the color of an alert item from red to black to signal that an alert has been taken care of. After an alert has been raised, its color automatically changes to in Unified RTMT and stays that way until you manually clear the alert.

Clear All Alerts: This menu category allows you to clear all alerts. Reset all Alerts to Default Config: This menu category allows you to reset all alerts to the default configuration. Alert Detail: This menu category provides detailed information on alert events. Config Email Server: In this category, you can configure your email server to enable alerts.

Config Alert Action: This category allows you to set actions to take for specific alerts; you can configure the actions to send the alerts to desired email recipients. In Unified RTMT, you configure alert notification for perfmon counter value thresholds and set alert properties for the alert, such as the threshold, duration, frequency, and so on.

You can locate Alert Central under the Tools hierarchy tree in the quick launch. Alert Central provides both the current status and the history of all the alerts in the system. You can add and delete user-defined alerts in the performance-monitoring window; however, you cannot delete preconfigured alerts. The following table provides a list of fields that you may use to configure each alert; users can configure preconfigured fields, unless otherwise noted.

Descriptive name. For preconfigured alerts, you cannot change this field. See topics related to Alert Central displays for a list of preconfigured alerts. You cannot edit this field for preconfigured alerts. You cannot change this field. You can associate only one instance of the performance counter with an alert. This field is applicable only for alerts based on performance counters. Condition to raise alert how long value threshold has to persist before raising alert.

Options include the system sending the alert immediately or after a specified time that the alert has persisted. Raise alert only when a configurable number of events exceeds a configurable time interval in minutes.

For ExcessiveVoiceQualityReports, the default thresholds equal 10 to 60 minutes. This field is applicable only for event based alerts. This field is applicable only for non-clusterwide alerts. When you deactivate both the Cisco CallManager and Cisco TFTP services of a server, the system considers that server as removed from the currently monitored server list.

ID of alert action to take System always logs alerts no matter what the alert action. Alert action is defined first see the Alert Customization topic. A blank field indicates that e-mail is disabled. Resets alert change the color of an alert item from red to black to signal that the alert is resolved.

After an alert is raised, its color automatically changes to black and remains until you manually clear the alert. Use Clear All to clear all alerts.

For ExcessiveVoiceQualityReports, RouteListExhausted, and MediaListExhausted, up to 30 current event details display in the current monitoring interval if an alert is raised in the current interval. Otherwise, the previous 30 event details in the previous interval displays.

How often to generate alert when alert condition persists. Specify every X minutes. Raise alert once every X minutes if condition persists. Specify every X minutes up to Y times. Raise alert Y times every X minutes if condition persists. Administrator to append text on top of predefined alert text. For viewing purposes for example, show only Sev. Specify defaults that are provided for predefined for example, Error, Warning, Information alerts. The alert log stores the alert, which is also stored in memory.

The memory is cleared at a constant interval, leaving the last 30 minutes of data in the memory. When the service starts or restarts, the last 30 minutes of the alert data load into the memory by the system reading from the alert logs on the server or on all servers in the cluster if applicable. The alert data in the memory is sent to the RTMT clients on request.

The alert log is periodically updated, and new logs are inserted into the log history window. After the number of logs reaches , RTMT removes the oldest 40 logs. The first line of each log file comprises the header. Details of each alert are written in a single line, separated by a comma. Log Partition Monitoring LPM , which is installed automatically with the system, uses configurable thresholds to monitor the disk usage of the log partition on a server.

The Cisco Log Partition Monitoring Tool service starts automatically after installation of the system. Every 5 minutes, Log Partition Monitoring uses the following configured thresholds to monitor the disk usage of the log partition and the spare log partition on a server:. To save the log files and regain disk space, you can use trace and log central option in RTMT.

In addition, Cisco Log Partitioning Monitoring Tool service checks the server every 5 seconds for newly created core dump files. To utilize log partition monitor, verify that the Cisco Log Partitioning Monitoring Tool service, a network service, is running on Cisco Unified Serviceability on the server or on each server in the cluster if applicable.

Stopping the service causes a loss of feature functionality. When the log partition monitoring services starts at system startup, the service checks the current disk space utilization. If the percentage of disk usage is above the low water mark, but less than the high water mark, the service sends a alarm message to syslog and generates a corresponding alert in RTMT Alert central. To offload the log files and regain disk space on the server, you should collect the traces that you are interested in saving by using the Real-Time Monitoring tool.

If the percentage of disk usage is above the high water mark that you configured, the system sends an alarm message to syslog, generates a corresponding alert in RTMT Alert Central, and automatically purges log files until the value reaches the low water mark. Log Partition Monitoring automatically identifies the common partition that contains an active directory and inactive directory.

Your browser is incompatible with this site. Upgrade to a different browser like Google Chrome or Mozilla Firefox to experience this site. It is available for both Windows- and Linux-based PCs or laptops. New features may be added to RTMT as new versions of applications evolve.

These provide you with a snapshot of your environment right out of the box without creating any customized views. However, in many cases, you may wish to create your own customized views of a variety of performance monitors. Not only that, you also might wish to create different views for different servers and applications in your environment. You can achieve this by creating your own personalized profiles, which can be saved for future use. You can switch between profiles during a single RTMT session, or you can open a profile during future access to see a consistent view of performance counters each time you log in.

To create a personalized profile, open the desired performance monitors and then take the following steps:.