With thresholds users have the ability to create customized alarms based on a wide selection of criteria, including:
OS metrics, voice quality, trunk utilization, and license utilization.
Creating a Threshold
Thresholds can be created in Capacity Manager, under: Customer Menu -> Capacity Manager -> Thresholds
On the thresholds page, click 'Add Threshold'
After a threshold is created, a new rule and workflow will also need to be configured. To do this:
Configure an alarm rule that will be run when the threshold is triggered.
Create a workflow to be run when the alarm rule matches the threshold that was triggered.
Check and confirm the threshold -> alarm rule -> workflow configuration.
Available Thresholds
Announcement Board Seconds Remaining
The 'Announcement Board Seconds Remaining' threshold will be triggered when the available time remaining for the selected Announcement Board, reaches, or breaches the specified number of seconds.
The current value is based on the 'List Integrated-ann-boards' Avaya Communication Manager command.
The name of the threshold alarm raised is 'Announcement Board Threshold'
CDR Buffer Utilization
Avaya ACM CDR buffer utilization, measures how much call detail data is currently buffered. Buffering occurs when the CDR link is down, or is experiencing problems. Any buffer utilization may be indicative of network issues and should warrant investigation.
This threshold can be set on the primary or secondary CDR link. Where only one link is configured it will be selected by default.
The name of the threshold alarm raised is 'CDR Buffer Utilization Threshold'
CPU
The 'CPU' threshold will be triggered when the percentage of utilized CPU, reaches, or breaches a specified value.
The threshold can be configured across Windows and Linux servers, and for all equipment types.
The name of the threshold alarm raised is 'CPU Threshold'
Disk
The 'Disk' threshold will be triggered when the percentage of used Disk space on a selected volume, reaches, or breaches a specified value.
For example, raise an alarm when disk volume /dev/sda5 on server Avaya-CM is >90% full.
The threshold can be configured across Windows and Linux servers, and for all equipment types.
The name of the threshold alarm raised is 'Disk Threshold'
IPNR Endpoint De-registration
IPNR Endpoint De-registration threshold triggers an alarm when the total % of de-registered endpoints for selected IPNRs in the last specified time interval reach, or breach the specified threshold.
Unlike other thresholds, any alarms triggered by this threshold will not auto-resolve.
The name of the threshold alarm raised is 'IPNR Endpoints deregistration'
IPSI Missed Heartbeats
Avaya IPSI thresholds are configured based on the port network and use the same criteria as the historic IPSI reports under Availability manager.
For a selected ACM, a threshold can be created to raise an alarm when the number of hearbeats on a selected IPSI board reaches, or breaches a specified number of heartbeats.
The name of the threshold alarm raised is 'IPSI Missed Heartbeats Threshold'
IPSI Round Trip Delay
Avaya IPSI thresholds are configured based on the port network and use the same criteria as the historic IPSI reports under Availability manager.
For a selected ACM, a threshold can be created to raise an alarm when the round trip delay on a selected IPSI board reaches, or breaches a specified number of seconds.
The name of the threshold alarm raised is 'IPSI Round Trip Delay Threshold'
License Utilization
The license utilization for Avaya Communication Managers, Enablement Servers, and Call Management Systems can be monitored via thresholds.
For the selected equipment, a threshold can be created to raise an alarm when for a selected license type, the number of utilized licenses reaches, or breaches a specified percentage.
For example: For Avaya ACM, create a threshold alarm, when the 'Logged-In SIP EAS Agents' license is 80% utilized.
Memory
The 'Memory' threshold will be triggered when the percentage of utilized Memory, reaches, or breaches a specified value.
The threshold can be configured across Windows and Linux servers, and for all equipment types.
The name of the threshold alarm raised is 'Memory Threshold'
Trunk Group Utilization
The 'Trunk Group Utilization' threshold is triggered when the number of utilized trunks for a selected trunk group reaches or breaches a specified percentage.
The 'Trunk group capacity' threshold is based the 'Total Usage' value in a trunk group summary last hour report command in Avaya Communication Manager, for a specific trunk group number. The report is run hourly.
The name of the threshold alarm raised is 'Trunk Group Usage Threshold'
Trunks in Trunk Group Out of Service
The 'Trunks in Trunk Group Out of Service' threshold is triggered when the number of out-of-service trunks for a selected trunk group reaches or breaches a specified percentage.
The name of the threshold alarm raised is 'Trunk Group Out of Service'
VQM MOS Summary
The 'VQM MOS Summary' threshold is triggered when average MOS on all streams in the past hour against the selected RTCP Receiver reaches or breaches a specified percentage, for selected IP Network Regions.
A typical use case would be to raise an alarm if poor voice quality traffic on a specified network region exceeds 5% - and the threshold for this would be:
For RTCP Receiver <my RTCP Receiver> raise an alarm when <5%> of streams have MOS <= 3.6 on IPNR = <my IPNR>
The name of the threshold alarm raised is 'VQM MOS Threshold'
Genesys Long Conversation
The Genesys Long Conversation threshold is triggered when a conversation is greater than or equal to the value set (minutes) in the criteria.
Genesys Short Conversation
under development