Supported Metrics
The following tabs represent the Metric Category of Poly VOIP Phone
Native Type | Metric Name | Display Name | Units | Application Version | Description |
---|---|---|---|---|---|
Poly VOIP Phone | poly_voip_phone_SIP_Status | SIP Status | 1.0.0 | Provides line info Registration Status. Possible outcomes are - 0 - Unregistered, 1 - Registered | |
poly_voip_phone_Packets_Lost | Data Packets Lost | count | 1.0.0 | Provides packets lost information while transmission | |
poly_voip_phone_AppState | AppState | 1.0.0 | Provides polycom device state info. Possible outcomes are 0 - Unknown, 1 - AppStateMenu, 2 - AppStateCall |
Native Type | Metric Name | Display Name | Units | Application Version | Description |
---|---|---|---|---|---|
Poly VOIP Phone | poly_voip_phone_Free_Memory | Free Memory in Mbytes | MB | 1.0.0 | Provides device free memory details |
Native Type | Metric Name | Display Name | Units | Application Version | Description |
---|---|---|---|---|---|
Poly VOIP Phones | poly_voip_phone_TxMOSLQ | Local Conversational MOS Score | count | 1.0.0 | The ranking/score of the quality of voice and video sessions obtained from local listening quality tests |
poly_voip_phone_RxMOSLQ | Remote Conversational MOS Score | count | 1.0.0 | The ranking/score of the quality of voice and video sessions obtained from remote listening quality tests | |
poly_voip_phone_TxMOSCQ | Local Listening MOS Score | count | 1.0.0 | The ranking/score of the quality of voice and video sessions obtained from local conversational quality tests | |
poly_voip_phone_RxMOSCQ | Remote Listening MOS Score | count | 1.0.0 | The ranking/score of the quality of voice and video sessions obtained from remote conversational quality tests | |
poly_voip_phone_Latency | Latency | ms | 1.0.0 | The time it takes for some data to get to its destination across the network | |
poly_voip_phone_Max_Jitter | Max Jitter Time | ms | 1.0.0 | Maximum Variation in time delay between when a signal is transmitted and when it's received over a network connection | |
poly_voip_phone_Jitter | Jitter Time | ms | 1.0.0 | Variation in time delay between when a signal is transmitted and when it's received over a network connection |
Native Type | Metric Name | Display Name | Units | Application Version | Description |
---|---|---|---|---|---|
Poly VOIP Phone | poly_voip_phone_current_CPU_Utilization | Current CPU Utilization | % | 1.0.0 | Current CPU utilization of the device. |
poly_voip_phone_average_CPU_Utilization | Average CPU Utilization | % | 1.0.0 | Average CPU utilization of the device | |
poly_voip_phone_Memory_Utilization | Memory Utilization | % | 1.0.0 | Provides device memory usage details | |
poly_voip_phone_Used_Memory | Memory Used in Mbytes | MB | 1.0.0 | Provides the amount of memory used |
Default Monitoring Configurations
Poly VOIP Phone 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 requirement by cloning respective Global Templates and Global Device Management Policies. It is recommended to clone them 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:
{appName nativeType - version}
Ex: poly-voip-phone Poly VOIP Phone - 1 (i.e, appName = poly-voip-phone, nativeType = Poly VOIP Phone, 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}
Ex: poly-voip-phone Poly VOIP Phone Template - 1 (i.e, appName = poly-voip-phone, nativeType = Poly VOIP Phone, 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}
Ex: Poly VOIP Phone Monitor poly-voip-phone Poly VOIP Phone 1 (i.e, monitorKey = Poly VOIP Phone Monitor, appName = poly-voip-phone, nativeType = Poly VOIP Phone, version = 1)