Time-based escalation chains with 8-5 M-F and the inverse?
I’m trying to set up an escalation chain for a group where it does one behavior from 8-5 Monday through Friday, but also in the same escalation chain, we want anything OUTSIDE that time to follow anotther behavior. Unfortunately, I see 3problems. It looks like I’m going to have to make 4 different subchains. a) weekends, b) midnight to 8 am, c) 8 am to 5 pm, and d) 5pm to midnight It looks like LM wont let me select 24:00 to make sure the gap is closed, so I’m worried about alerts that happen between 23:45 and 24:00 (00:00 next day) It also bugs me that technically the way I’m doing it below, I have 2 subchains that apply to the 8:00 minute and the 17:00 minute (5 pm) as each of those moments are included in subchains that overlap on that one minute Does anyone have a better solution to this? What do I do about #2 above in particular? Thanks!Solved60Views9likes1CommentEscalation Chain text ACK notification, send to all users in alert stage
Some teams operate primarily through text and as such their escalation chains are set that way. The utility of an ACK notification to all members of the escalation chain stage gets lost when it is sent by a method, email, not even used in the escalation chain. This notification should use the same delivery method used in that stage to send the original alert. (https://www.logicmonitor.com/support/alerts/responding-to-alerts/responding-to-native-sms-alert-notifications/see description in table for ACK). This has been tested and email is the only method that will notify users, request is to have functionality put in place to send all users in alerting escalation chain the ACK notification instead of through email only. Thanks1View0likes0CommentsAdd Escalation Chain UI
The Add a new chain> Add new recipients dialog seems to suggest that only users can be added, but in fact allows groups also. Please enhance the UI captions to make clear if one or both is possible. It's confusing to my users and generates unnecessary tickets.3Views0likes0Comments