We recently had an issue where our AES went into TOO_MANY_LICENSES against the DMCC API.
On our AES alerts, we didnt pick up on this and looking at the defaults its only looking for server_connection
What syntax can I use to be notified when the server is in the TOO MANY state for DMCC?
I am aware that there is a record but unsure how this should be built to ensure we get a trap.
Also, by setting these values does it mean that Prognosis is checking for this value and if so, what frequency will it be checking for it?
Thanks for reading.
The standard AES_Alerts threshold has conditions detecting the AES license usage > 90% or 100% at every 10 seconds, the record is AvayaAesLicenseUsageSummary. Was this threshold running at the time the too_many event occured?
The threshold was running and we are using the standard AES alerts- I also noticed on the thresholdits looking for server conection errors(our error was TOO MANY LICENCES)
AESDMCLM.STD = 2 OR AESDMCLE ="serverConnection"
If I updated the syntax as below woudl that also flag if the server enterted this state?
OR AESDMCLE =" tooManyLicences"
That will work if you change the condition to detect the tooManyLicenses state. You can also test it in a display to make sure the data shows up as expected, then implement it in the threshold document.
Unified Communications has always been an important part of companies' digital transformation efforts due to its ability to enable rich virtual collaboration and communication. But with COVID-19, we've reached a break-through point.
Join Bill Haskins, Sr. Analyst & Partner, Unified Communications at Wainhouse Research, and John Ruthven, CEO at IR discuss UC challenges companies are experiencing due to the COVOID-19 crisis.Join webinar