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?36Views2likes5CommentsUptime - Bug Report
I’d like to re-initiate this bug report. The Uptime resetting counters at 497 days or 469 days (historical) I just had a similar false alarm telling me that my devices rebooted, when they did not. Please have the DEV team review this specific monitor and determine how the system can display 497+ days “uptime” --------------------------------- ________________________________________ SEP 11, 2015 | 01:56PM CDT Original message ________________ wrote: Support team at logic monitor, Is it possible to request adjustment to the "Uptime" data source monitor so that it does not alert when the counter resets from 11111111111111111111111111111111 to 00000000000000000000000000000001 The developer was aware enough of the event cause to code explanation in to the system alert: could the alert be altered to not-alert when the counter resets? - ________________ From: ________________ Sent: Friday, September 11, 2015 2:44 PM To: Subject: SC# Error: 6348 ________________ is reporting it has only been up for 0.43 minutes Hello ________________ , We have received the following monitoring alert and a ticket #6348 has been created to track your issue. An engineer is assigned and is working to resolve this issue. Thank you. We are investagating if the VM really did reboot or if this alert is coming up for a different reason: ________________is reporting it has only been up for 0.43 minutes, as of 2015-09-11 14:28:48 EDT. If this was an unexpected reboot, please investigate the system logs. NOTE: if ________________has been up for 469 days without a reboot, this alert will trigger due to a counter wrap in the host. In this case, you may disregard this alert. (But the host is probably due for an OS update.) For any inquiries please contact our NOC at support@highpoint.com<mailto:support@highpoint.com> or call 1-855-485-8324 (TECH). Regards, ________________ NOC Support Engineer23Views0likes1Comment