We added a second thread and configured the primary notification engine escalation, "SYS:NPC:IM1-TriggerGroupNTG", to use that thread. We have significant notification volume based on some standard Service Targets, and this escalation is on a one minute poll. Bottom line, identify your "high intensity" escalations and assign them to a separate pool to avoid having them impact the other escalations.
-- Chris Danaceau This e-mail and its attachments are confidential and solely for the intended addressee(s). Do not share or use them without Fannie Mae's approval. If received in error, contact the sender and delete them. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Begosh, Kevin Sent: Tuesday, October 28, 2008 11:11 AM To: arslist@ARSLIST.ORG Subject: Escalation Threads ** I was wondering does anyone know what a good numbering is for the AR Escalation threads, min/max. We have a Large system, with about 100,000 incidents just to give you an idea. We have all applications, Service Desk, Change Management, CMDB, Asset, SLM etc... For some reason our escalations started to almost stop the other day and we looked and it was set to 1:1. Kevin Begosh, RSP __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
