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.88 release will be rolled out through the end of April. This release will be on the smaller side, but we fit several cool new features/improvements into it, namely AWS cross-account role authentication and “Test Script” for DataSource Active Discovery and EventSources.
Additionally, we are introducing a new section to our release notes: LogicModule Releases. Take a look below to ensure your monitoring is up-to-date!
AWS Cross-Account Role Authentication
We are adding support for AWS cross-account roles as a method of authentication for AWS CloudWatch data collection. Instead of using an AWS Access ID/Secret Key to authenticate CloudWatch data requests to your account, LogicMonitor will use a designated IAM role.
Why is this important? Authenticating via a cross-account role offers more security benefits than via the use of Access ID and Secret Key. As such, it is the preferred method of authentication by AWS.
What impact will this have on my account? All new AWS accounts in LogicMonitor will need to provide a role ARN rather than the Access ID and Secret Key pair. Existing AWS accounts in LogicMonitor will continue to authenticate via AWS Access ID and Secret Key, but updates will not be permitted for AWS Access ID and Secret Key information. Instead, a role ARN must be provided to update authentication information. Updates to non- authentication information are allowed and you can continue to test Access ID and Secret Key credentials via the “Test” button.
Test Script for DataSource Active Discovery and EventSources
We are adding the ability to test your DataSource Active Discovery and EventSource scripts, which enables you to tentatively apply your scripts to a device and view their respective outputs.
Using Test Script for Active Discovery will display a table of instances that would be discovered for the designated device. For EventSources, Test Script will return a table of events that would be discovered for the selected device.
Why is this important? If you are not seeing an instance or event that you expect, Test Script enables you to determine if it is not being discovered or is not passing filter criteria. It can also increase efficiency and save time during LogicModule development.
REST API
We are releasing the Ops Notes resource with version 1.2.1 of our REST API:
With the REST API Ops Notes resource, you can programmatically manage Ops Notes for your LogicMonitor account. This is useful if you’re using Ops Notes to identify/annotate routine events (e.g. deployments) because it enables you to automate the creation of a note within your existing workflows.
While we’ve always recommended URL encoding special characters in the URL (i.e. query parameter values), v88 includes a change that requires “{” and “}” characters be URL encoded if these characters are present in query parameter values. This also applies to the RPC API.
Other Improvements
Alerts
Collectors
Dashboards
Integrations
Netflow
Services
Settings
Bugs Fixed
LogicModule Releases
Below is a full list of new/improved LogicModules as well as bug fixes that were implemented since our last release:
New Monitoring Coverage
< li style="font-weight: 400;">AWS EC2 Scheduled Events: 1 DataSource
Monitoring Fixes & Updates