March 2011 release

These are the release notes for the March, 2011 LogicMonitor release, which will be applied to servers this week. (Account administrators will be notified on the applicable update time).

New Features

  • syslog event monitoring
  • extension to the groovy toolset, allowing easy scripting of arbitrary HTTP transactions.
  • the ability to change the time range of regular host graphs when shown on a dashboard. (Click the pencil icon on the widget, select a new time frame, and submit)
  • Wizard to aid in constructing Applies To fields. When defining datasources or dynamic groups, you can now use a Wizard to construct the LMS expression that controls which hosts will be associated with the group or datasource.
  • The CC field is always notified when a new SDT is created. (Previously, it was an optional checkbox)
  • Significant improvements in Windows Event Log monitoring – cleaner display, autocomplete for event source filters
  • You can now select hosts by group, as well as host name pattern matching, for SLA reports, metric trend reports
  • The comments included in a reply to an alert, that also creates a SDT, will now be included in the notification message sent to those to whom the alert has been sent to. (e.g. if an alert is replied to with “SDT 7 will check in morning”, then the “will check in morning” comment will be included in the message sent to others that the alert had been sent to.)
  • enhancements to the embedded Expect client.
  • The ability to disable the “Chat with Engineer” button on an account wide basis. (Currently you have to contact support to disable the button. Role base control will be coming soon.)
  • Expanded tokens available for event alert messages
  • More information is automatically collected about ESX hosts (CPUs, hardware model, etc)
  • Added the ability to reinstall an existing agent

Other Changes

The http collector uses a different library in this release. The significance of this is that reported HTTP page time now includes the connection setup time – previously, that time was not reported.  This will only significantly affect results for long latency measurements – for example, those page response times being collected by an agent several thousand miles away will show an increase in reported page load time.

UI Changes

  • The Suppress button (which scheduled SDT for the instance in alert starting at the present moment) is now part of the Acknowledge form.
  • Comments now required in acking an alert.
  • simplified log in screen – the company field, which was always pre-filled, is now hidden entirely
  • changed “Test alert” icon to “Show alert routing”, to clarify that it does not trigger alerts, but simply shows the routing alerts will be subject to.
  • snmp interface descriptions no longer repeat the interface name before the description
  • agents are now referenced by their description, not just numeric ID, when reporting agent down, or when confirming agent deletion
  • ESX, JMX, memcached, Perfmon and Xen specific datasources have had the UI definition greatly simplified. (Other collectors will have the same improvements applied next release)
  • The duration for Scheduled Downtime is now calculated and shown when start and end times are used.
  • when viewing a host, the System information (the OS version, display name, and other discovered properties) are now separated into the System tab, while user set properties are in the “Customized Properties” tab.

Bugs Fixed

  • corrected an issue where tasks with long periods between collections would sometimes not be scheduled correctly if other collecting tasks changed frequently.
  • The relative ordering (Display Priority) of overview graphs was not respected.
  • Search results were broken on the Reports tab
  • special characters (e.g. “/?! ) now display correctly in graph titles.
  • sms template was not used, even though a user had SMS format paging preference defined.

In this Article: