Supported Metrics
The following tabs represent the Metric Category of Cisco UCM app.
Native Type | Metric Name | Display Name | Units | Application Version | Description |
---|---|---|---|---|---|
Cisco UCM | ciscoucm_node_ServiceStatus | CiscoUCM Node Service Status | 1.0.0 | Service status information for a system. Possible values are - Started : 0 ,Starting : 1 ,Stopping : 2 ,Unknown : 3 ,Stopped : 4. | |
ciscoucm_callmanager_CallManagerHeartBeat | CiscoUCM CallManager CallManagerHeartBeat | count | 1.0.0 | The heartbeat of CallManager. This is an incremental count that indicates that CallManager is alive and running. If the count does not increment, then CallManager is down (dead). | |
Cisco UCM Phone | ciscoucm_phone_Status | CiscoUCM Phone Status | 1.0.0 | The phone registration status type. Possible values are - Any : 0 , Registered : 1, Unregistered : 2 , Rejected : 3 , PartiallyRegistered : 4, Unknown : 5. | |
Cisco UCM SIPTrunk | ciscoucm_siptrunk_Status | ciscoucm siptrunk Status | 1.0.0 | The siptrunk registration status type. Possible values are - Any : 0 , Registered : 1, Unregistered : 2 , Rejected : 3 , PartiallyRegistered : 4, Unknown : 5. |
Native Type | Metric Name | Display Name | Units | Application Version | Description |
---|---|---|---|---|---|
Cisco UCM | ciscoucm_callmanager_AverageExpectedDelay | CiscoUCM CallManager AverageExpectedDelay | count | 1.0.0 | The current average expected delay to handle any incoming message. |
ciscoucm_processor_CPUTime | CiscoUCM Processor CPUTime | % | 1.0.0 | The processor's share of the elapsed CPU time excluding the idle time since last update, expressed as a percentage of CPU time. | |
ciscoucm_network_RxBytes | CiscoUCM Network RxBytes | Bytes | 1.0.0 | The number of bytes, including framing characters, that was received on the interface. | |
ciscoucm_network_TxBytes | CiscoUCM Network TxBytes | Bytes | 1.0.0 | The total number of octets, including framing characters, that was transmitted out of the interface. | |
ciscoucm_network_TotalBytes | CiscoUCM Network TotalBytes | Bytes | 1.0.0 | The total number of received (Rx) bytes and transmitted (Tx) bytes. | |
ciscoucm_network_TotalPackets | CiscoUCM Network TotalPackets | count | 1.0.0 | The total number of received (Rx) packets and transmitted (Tx) packets. | |
ciscoucm_network_RxErrors | CiscoUCM Network RxErrors | count | 1.0.0 | The number of inbound packets and the number of inbound transmission units that contained errors that prevented them from being deliverable to a higher layer protocol. | |
ciscoucm_network_TxErrors | CiscoUCM Network TxErrors | count | 1.0.0 | The number of outbound packets and the number of outbound transmission units that could not be transmitted because of errors. | |
ciscoucm_network_RxPackets | CiscoUCM Network RxPackets | count | 1.0.0 | The number of packets that this sublayer delivered to a higher sublayer. This does not include the packets that were addressed to a multicast or broadcast address at this sublayer. | |
ciscoucm_network_TxPackets | CiscoUCM Network TxPackets | count | 1.0.0 | The total number of packets that the higher level protocols requested for transmission, including those that were discarded or not sent. |
Native Type | Metric Name | Display Name | Units | Application Version | Description |
---|---|---|---|---|---|
Cisco UCM | ciscoucm_callmanager_CallsActive | CiscoUCM CallManager CallsActive | count | 1.0.0 | The number of voice or video streaming connections that are currently in use. |
ciscoucm_callmanager_CallsAttempted | CiscoUCM CallManager CallsAttempted | count | 1.0.0 | The total number of attempted calls. | |
ciscoucm_callmanager_CallsCompleted | CiscoUCM CallManager CallsCompleted | count | 1.0.0 | The number of calls that were actually connected (a voice path or video stream was established) through this CallManager. This number increments when the call is terminated. | |
ciscoucm_callmanager_CallsInProgress | CiscoUCM CallManager CallsInProgress | count | 1.0.0 | The number of voice or video calls that are currently in progress on this CallManager, including all active calls. | |
ciscoucm_callmanager_VideoCallsActive | CiscoUCM CallManager VideoCallsActive | count | 1.0.0 | The number of active video calls with active video streaming connections on all video conference bridge devices registered with this CallManager. | |
ciscoucm_callmanager_VideoCallsCompleted | CiscoUCM CallManager VideoCallsCompleted | count | 1.0.0 | The number of video calls that were actually connected with video streams and then released. | |
ciscoucm_callmanager_VideoOutOfResources | CiscoUCM CallManager VideoOutOfResources | count | 1.0.0 | The total number of times CallManager attempted to allocate a video streaming resource from one of the video conference bridge devices that is registered to this CallManager when none were available. | |
ciscoucm_memory_MemUtilization | CiscoUCM Memory MemUtilization | % | 1.0.0 | The percentage of system physical memory utilization on the system. |
Native Type | Metric Name | Display Name | Units | Application Version | Description |
---|---|---|---|---|---|
Cisco UCM | ciscoucm_callmanager_AnnunciatorOutOfResources | CiscoUCM CallManager AnnunciatorOutOfResources | count | 1.0.0 | The total number of times that CallManager attempted to allocate an annunciator resource from those that are registered to this CallManager when none were available. |
ciscoucm_callmanager_HWConferenceOutOfResources | CiscoUCM CallManager HWConferenceOutOfResources | count | 1.0.0 | The total number of times CallManager attempted to allocate a hardware conference resource from those that are registered to this CallManager when none were available. | |
ciscoucm_callmanager_LocationOutOfResources | CiscoUCM CallManager LocationOutOfResources | count | 1.0.0 | The total number of times that a call through Locations failed due to lack of bandwidth. | |
ciscoucm_callmanager_MOHOutOfResources | CiscoUCM CallManager MOHOutOfResources | count | 1.0.0 | The total number of times that the Media Resource Manager attempted to allocate an MOH resource when all available resources on all MOH servers registered with this CallManager were already active. | |
ciscoucm_callmanager_MTPOutOfResources | CiscoUCM CallManager MTPOutOfResources | count | 1.0.0 | The total number of times CallManager attempted to but failed to allocate an MTP resource from one of the MTP devices that is registered with this CallManager. | |
ciscoucm_callmanager_RegisteredAnalogAccess | CiscoUCM CallManager RegisteredAnalogAccess | count | 1.0.0 | The number of registered Cisco Analog Access gateways that are registered with this system. | |
ciscoucm_callmanager_SWConferenceOutOfResources | CiscoUCM CallManager SWConferenceOutOfResources | count | 1.0.0 | The total number of times CallManager attempted to allocate a software conference resource from those that are registered to this CallManager when none were available. | |
ciscoucm_callmanager_TranscoderOutOfResources | CiscoUCM CallManager TranscoderOutOfResources | count | 1.0.0 | The total number of times CallManager attempted to allocate a transcoder resource from one of the transcoder devices that is registered to this CallManager when none were available. | |
ciscoucm_callmanager_VCBOutOfResources | CiscoUCM CallManager VCBOutOfResources | count | 1.0.0 | The total number of times that CallManager attempted to allocate a video conference resource from those that are registered to this CallManager when none were available. |
Default Monitoring Configurations
Cisco UCM has default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. You can customize these default monitoring configurations as per your business use cases by cloning respective global templates and global Device Management Policies. OpsRamp recommends performing the below activity before installing the application to avoid noise alerts and data.
Default Global Device Management Policies
You can find the Device Management Policy for each Native Type at Setup > Resources > Device Management Policies. Search with suggested names in global scope. Each Device Management Policy adhers the following naming convention:
{appName nativeType - version}
Example: cisco-ucm Cisco UCM - 1 (i.e, appName = cisco-ucm, nativeType =Cisco UCM, version = 1)
Default Global Templates
You can find the Global Templates for each Native Type at Setup > Monitoring > Templates. Search with suggested names in global scope. Each template adheres to the following naming convention:
{appName nativeType 'Template' - version
Example: cisco-ucm Cisco UCM Template - 1 (i.e, appName = cisco-ucm , nativeType = Cisco UCM, version = 1)
Default Global Monitors
You can find the Global Monitors for each Native Type at Setup > Monitoring > Monitors. Search with suggested names in global scope. Each Monitors adheres to the following naming convention:
{monitorKey appName nativeType - version}
Example: Cisco UCM Monitor cisco-ucm Cisco UCM 1 (i.e, monitorKey = Cisco UCM Monitor, appName = cisco-ucm , nativeType = Cisco UCM, version= 1)