Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
Configuring SDT (scheduled downtime) allows you to suppress all routed alert notifications during periods when alerts are expected as a result of upgrades, maintenance or other scheduled activities. This functionality is ideal for eliminating alert noise around activities that are planned and, therefore, aren’t cause for alarm.
However, many LogicMonitor users place resources into SDT on an impromptu basis for the purpose of temporarily suppressing recurring or escalating alert notifications while troubleshooting the root cause of an alert. And while this is effective for reducing alert noise, it also means that alert clear notifications were not routed once the issue was resolved. For users that route alert notifications to third-party applications for the purpose of opening and closing tickets in those applications, the lack of an alert clear notification can result in orphaned tickets.
To reduce the incidence of orphaned tickets in third-party applications, LogicMonitor is introducing new default behavior for alert clear notifications while SDT is in place. With the release of v.133, any alert rule that has the Send notification when alerts clear option checked (this option is checked by default) will always route an alert clear notification for any DataSource alert previously routed. In other words, if a DataSource alert notification was routed, an alert clear notification will also be routed, even if the resource is subsequently placed into SDT after the initial notification is routed.
This new default behavior helps close the loop in third-party applications, ensuring that tickets automatically opened by alert notifications are also automatically closed when the alert clears.
Note: This behavior is only in place for alerts triggered by DataSources.
When moving resources via dragging and dropping, any resources on outgoing connections to the resourcing being moved are moved along with it. This improved behavior makes it easier to move resources in bulk without the need to drag each individual resource into position. If a connection has multiple edges for incoming and outgoing, then the resources will continue to move independently of each other.
Upon your account’s upgrade to v.133, import our new and updated LogicModules from the LogicMonitor repository to expand and enhance your monitoring coverage.
The addCategory_HyperV PropertySource has been updated to identify versioning information in order to support the new, consolidated DataSource.
If you are currently using the legacy DataSources, you will not experience any data loss upon importing the new DataSource because of the name variation. However, you will collect duplicate data and potentially receive duplicate alerts for as long as the legacy DataSources are active. For this reason, we recommend that you disable the legacy DataSources after importing the new one.
In This Article