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!
Happy New Year! We’re kicking off 2019 with a robust release. v.114, which will be rolled out through the middle of January, features many impactful new features and improvements.
Two exciting new features are being released with v.114 to help you better manage alerts and their notifications!
Secondary sorting using an alert’s severity status and time began timestamp is now available from any area of the LogicMonitor interface that features an alerts table (e.g. Alerts page; Alerts tab for a device, cloud resource, or website; Alert List dashboard widget). This improvement allows users to simultaneously sort on both the alert severity level (primary sort) and the time alert began (secondary sort), and was implemented to provide more logical context when viewing alert lists.
To turn on secondary sorting for an alerts table, click on the icon ( ) that acts as the header for the far left alert severity column. This automatically sorts using the chosen ascending/descending orders of both the alert severity and “Began” columns. To turn off secondary sorting, simply click on a column other than the “Began” column (or click the icon twice more) to reset the table to a single sort order. For more information on this new sorting capability (and other filter/sort options available for alerts), see Alerts Page Overview.
You can now route alert notifications based on properties that have been assigned to a resource (e.g. device, cloud resource) or website. This new property filter is available from the configuration settings of an alert rule. For more information on this new alert rule configuration (and other configurations available for routing alert notifications), see Alert Rules.
We are retiring our hosted Los Angeles checkpoint location with v.114. All Web Checks, Ping Checks, and Website Status widgets that reference the Los Angeles checkpoint will be automatically migrated to the San Francisco checkpoint, assuming it is not already in use.
Important! Some LogicMonitor configurations that reference the Los Angeles checkpoint must be manually updated to the San Francisco location in order to ensure that alert conditions are still properly brought to your attention. These configurations include:
LogicMonitor has long supported out-of-the-box and custom integrations to allow your organization to view and respond to LogicMonitor alerts via collaboration tools external to LogicMonitor. Now, with the introduction of the Integrations logs (available by navigating to Settings | Integrations | Logs), administrators have visibility into the outgoing and response payloads for every integration call made for improved troubleshooting. The Integrations logs can be filtered using a variety of criteria including delivery status (i.e. successful/failed) status, integration instance, and date/time to identify issues more quickly. For more information on this new feature, see Integrations Logs.
Note: This feature will be enabled after v.114 is fully rolled out.
We recently announced the new minimum required Collector. Please upgrade your Collectors to version 27.005 or higher as soon as possible, otherwise they will be auto-upgraded on Monday, February 25th, between 6-9PM PST. It is highly recommended that you upgrade prior to this time.
If SDT ends for a resource, but that resource remains in alert, it will then gain a higher priority status, causing it to move towards the top of the NOC widget, and providing better visibility into your infrastructure.
Next we’ve listed new and improved LogicModules that were implemented since our last release.
In This Article