v.70 Release: AWS S3, Instance Group Management, and Mobile

As v.70 will be the last release of the year, we are not releasing any major functionality.  You will find a number of improvements, such as the AWS S3 datasources and Instance Group Management, and an even larger number of bug fixes.  We have a lot in the works for 2016 that we look forward to sharing after the holiday season.

AWS Monitoring

We are now able to take advantage of AWS’s CloudWatch metrics for S3.  We removed our proprietary collection method and the need to use your collector for this data. The datasources utilizing AWS S3 as a collection method will be removed, CloudWatch data can be collected using the  AWS_S3 datasource.

Instance Group Management

As many of you transition away from the old UI view, we’ve heard two main complaints.  One is the device tree, which is currently in a prototype state and will optimistically be in v.71.  The other has been instance management.  The last release provided a lot of the basic functionality, but this release includes better Instance Group management.

To start, you will notice a new tab for Instances when you have selected a multi instance datasource in the device tree.

From this tab, you can select Add to create a new instance for a non Active Discovery datasource or add a new instance group.

The Actions button gives you the ability to bulk delete or move instances to a new instance group and Expand All will expand all instance groups.  This gives you the ability to easily review and update your instance groups.  Before you ask, yes, you can also drag and drop instances to a new group!

We’re not quite done, a similar view will be available from each instance group soon and we have a little clean up remaining on the Alert Tuning tab.

Alerts Table

The alerts table received another round of improvements from our design team.  Along with making the alert status more apparent, the font sizes were taken down a size and alternating row colors were added. We have a few more minor fixes in the works, and would love your feedback in the meantime.

More Services Features

The last release included a complete Services overhaul. Haven’t had time to check it out? Watch this two-minute overview video:

 

 

The Services improvements specific to this release are:

Default Settings 

Default Location and Alert Triggering configurations can be configured for your service checks.  This does not limit the options for any services in your account, but does allow you to manage your typical configuration across services in one place.

Users with rights to manage all services will see a button for Service Defaults next to the Manage button.

When creating or editing an individual service, you can opt to use the default settings.

If use default service settings is checked, any changes made to the Service Defaults will automatically apply to the service.

Please note, this is independent of managing locations by selecting your account name in the tree and clicking Manage.  Managing locations determines whether the location is available for the entire application.

Raw Data

A raw data tab is available for each service check.  Much like the raw data available for device instances, this provides a detailed view of the exact data LogicMonitor is storing per check.  This will be enhanced to include trace route information for Ping in the next release.

Properties for Authentication

The last release brought you properties to be used in Alerts.  Those properties can now also be used for authentication.

Mobile:

  • Fixed a bug with dashboards causing the app to crash for iOS.
  • The alerts view got some more love.  To start, dragging down will trigger a refresh.  Selecting the filter button in the upper right gives you the ability to auto filter by alert severity. 
  • Alert search will now return your last 10 searches and updates the alert list as you type.
  • The Acknowledge and SDT screens also received an update based on your feedback.  

Improvements:

  • The messaging for disabled monitoring has been improved to list all groups impacting the device.  If the user does not have rights to view the group, it will display as “Disabled at another group,” with a hover tip providing more detail.
  • Editing a widget datapoint is more friendly.  If you change the group or device, we will check to see if the datasource still applies.  If not, we’ll clear the datasource and datapoint fields for you. 
  • The Device NOC widget now supports grouping by Datapoint, providing the ability to go as broad or granular as you desire with your status display.
  • The Account Information page displays a breakdown of device count by device type.
  • The ConnectWise integration allows users to map a LogicMonitor alert severity level to a ConnectWise priority.
  • Device group has been added to the access log message when a cluster alert is modified.

Bugs:

  • We didn’t correctly account for how many integrations some of you have.  The list is now paginated.
  • When configuring a new integration, regular expression did not display as an option the first time the http response format was edited.
  • Viewing a graph for over 30 days with OpsNotes enabled resulted in a misaligned legend display.
  • A value was required in the UI for an active discovery filter of Exists, although a value is not needed.
  • A new device could only be added in the UI if a group was selected in the device tree.  
  • From the Device | Traffic tab, only one widget could be added to a dashboard.  For no good reason.
  • We only returned the last 24 hours of collector events, which isn’t always enough.  This has been extended to 7 days.
  • The custom graph widget can support up to 500 instances, but if this was exceeded an obscure error message displayed.
  • Clicking a Service name from an alert redirected to the Service page, but not the selected service.
  • Clicking on a breadcrumb after using Device Search did not always take you to the correct parent group.
  • Previously it was impossible to just update the contact method for a user in an escalation chain, the user also had to be re-selected.  We’ve simplified this.
  • There was not a clear error message if the alert rule escalation time was greater than the max value of 1440 minutes.
  • Users with limited device rights would receive a permission denied error when changing the zoom level.
  • The option to edit personal information did not work for roles where the settings section was set to view all.
  • In some situations complex datapoints were stored as the incorrect data type, resulting in gaps in graphs.
  • When creating a datasource with the script collection method, scripts could only be embedded directly.  We have fixed the upload script option.
  • An email address with a ‘+’ sign was rejected due to an invalid character.  This is now allowed.
  • You can now easily add a report group from the add dropdown.

In this Article: