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!
The v.105 Release will be rolled out through the end of May and first week of June. Among the improvements you will see are:
Azure Status Monitoring
Previously, Azure Cloud resource state (e.g. terminated, running, stopped) was only available via the system.azure.status property. We are introducing a new Azure Status DataSource for monitoring resource state, so you can monitor and alert on status over time. In addition to resource status, you will also see an accompanying explanation – e.g. customer initiated, outage, etc. We are retrieving this status data from the Azure Resource Health API, and it will be available for all Azure resources that this API supports. You may find this new status data useful for identifying when Azure resources are in an undesirable state and triggering alerts. We plan to extend this functionality to AWS in an upcoming release.
Auto-Filled Alert Thresholds
Previously, in order to enable color-change thresholds across the Gauge, Big Number, and Dynamic Table Widgets, you would have to manually assign the alert threshold values. With v.105, we will automatically populate these thresholds with values from the selected DataSource’s global definition. This both streamlines the widget setup process and ensures consistent thresholds are set across your account.
Other Improvements
Alerting
Dashboards
Devices
LM Cloud
LogicModules
Reports
REST API
Websites
Bugs Fixed
Monitoring Release Notes
Below is a list of new and improved LogicModules that were implemented since our last release:
New Monitoring Coverage
Monitoring Improvements