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!Solved60Views9likes1CommentSupport for chrony
Amazon Web Services (AWS) announced a free time synchronization service at re:Invent today. The announcement is at https://aws.amazon.com/blogs/aws/keeping-time-with-amazon-time-sync-service/. Interestingly they recommend that people uninstall NTP and install chrony instead. I tried this on a local Linux host and LM and get the following error: Alert Message: LMD2375 warn - 127.0.0.1 NTP ntpqNotFound ID: LMD2375 The ntpq binary was not found on the agent monitoring 127.0.0.1. Please install the ntpq binary (typically by yum install ntp, or apt-get install ntp) If LM customers running in AWS follow the recommendation their NTP monitoring will fail. Could / will LM support chrony in addition to ntpq?36Views2likes5Comments