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.92 release will be rolled out through the end of July. As mentioned in our last release, we are continuing a long-term initiative to improve our platform’s ease-of-use so you can gain maximum insight with the shortest possible workflows. As we crank away at these improvements, you may notice the next couple releases are a bit lighter. Some of the larger changes you will see in v.92 include:
Easy Collector Tuning You no longer have to manually edit the Collector’s configuration parameters in order to increase its monitoring capacity! Now, simply navigate to the Collector configuration window and select the desired Collector size (Small, Medium, or Large) from a dropdown menu. By making this selection, we will automatically update all necessary parameters in the Collector’s configuration file for you. This functionality requires a minimum Collector version EA 24.126.
Why you care: when a Collector (say, a Small or Medium Collector) reaches its monitoring capacity, you can now increase the number of devices it can monitor with the click of a button. This saves a substantial amount of time and mitigates the risk of human error when changing the Collector’s config.
Expanded Support for AWS Resources:
We have made the following changes to our AWS monitoring:
Why you care: these services can now be selected from the Add / Manage AWS Account Dialog, and LogicMonitor will discover resources and automatically begin monitoring CloudWatch metrics.
Why you care: this is useful if you have custom properties that need to be set for EC2 AutoScaling instances. By setting properties at the group level, you ensure all EC2 instances created for the AutoScaling group and auto-discovered by LogicMonitor inherit the correct properties.
We now include AWS account IDs in the billing data we monitor, which enables filtering by account ID in the AWS billing DataSources. You may find this useful for accounts configured to use consolidated billing, because it allows you to break out detailed costs to be per account.
REST API- version 1.4.3
Below is a full list of new/improved LogicModules as well as bug fixes that were implemented since our last release:
New Monitoring Coverage
Monitoring Fixes & Updates