| Summary: | ASTERISK-26559: app_queue: New service level calculation | ||
| Reporter: | Sebastian Gutierrez (sum) | Labels: | |
| Date Opened: | 2016-11-06 06:35:42.000-0600 | Date Closed: | 2017-01-10 14:02:22.000-0600 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_queue |
| Versions: | 13.12.1 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | This patch uses a new formula and add a new service level calculation taking in account the abandoned calls, if a call is abandoned inside the service level threshold this has to be computed as ok, this means the client didn't wait enough and this wont affect the SL Performance, but if the abandoned call is above the SL threshold then SL Performance will change.
Im adding SL2 so we can have both calculations. the SL2 calculation is a classic metric on contact centers. Changes in the patch provided: 1) add variable for counting the number of queue calls abandoned inside the servicelevel 2) when a call is abandoned then it checks if the time that the call was in queue was below or equals as the service level (now - starttime <= servicelevel) if this is true the we count them as abandoned inside the service level threshold. 3) a new service level SL2 is created using the following formula sl2 =100 * ((callsabandonedinsl +callscompletedinsl) /(callsabandoned callscompleted)); basically is total calls in service level / total calls 4) Added sl2 to AMI and queue show Just to comment this changes although I don't have test on the asterisk test suit for them, are tested heavily on production environments for at least a year now with no problems Tested in several servers that handle approximately 50.000 calls per day with no issues so far. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2016-11-06 06:35:43.951-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Martin Tomec (matesstar) 2016-12-28 03:34:24.902-0600 From my point of view, the previous service level calculation was wrong and this new is correct. So there is no need to show old (wrong) metric in queue status. Maybe it could be configurable as a queue parameter (servicelevelmetric = only_answered / include_abandoned). Or it should replace the previous metric completely as a bugfix. In this state (actual state in gerrit), it should be at least well documented for user. Because from "user" perspective I dont know which metric I should use - ServicelevelPerf or ServicelevelPerf2 ? By: Friendly Automation (friendly-automation) 2017-01-10 14:02:23.117-0600 Change 4682 merged by zuul: app_queue: add new Service Level calculation [https://gerrit.asterisk.org/4682|https://gerrit.asterisk.org/4682] | ||